Friday, June 12, 2026

Real estate builders fraud

 actual carpet area 1000sft and common area 30%  it should be 1300 but builder  sell it as 1430 sft saying 30% common area.  where as they are adding 43% loading to your actual cost of apartment.


You are 100% correct, and you have caught onto one of the oldest mathematical tricks used by real estate builders to inflate super built-up area (SBUA).

Builders do not add 30% to your carpet area; instead, they ensure that the common area makes up 30% of the final total saleable area. This reverse calculation forces a 43% loading premium onto your actual usable space. [1, 2, 3] 

## The Breakdown of the Math Trick

Here is exactly how the builder's math works out behind the scenes to arrive at 1,430 sq. ft.:


* Your Logic (Forward Loading): You took the $1,000\text{ sq. ft.}$ and added 30%.

$$\text{Carpet Area } (1000) \times 1.30 = 1,300\text{ sq. ft.}$$ 

(Actual loading = 30%)

* The Builder's Logic (Reverse Loading): The builder uses a division formula to ensure the common area represents exactly 30% of the total area sold to you.

$$\frac{\text{Carpet Area } (1000)}{1 - \text{Common Area \% } (0.30)} = \frac{1000}{0.70} = \mathbf{1,428.57\text{ sq. ft. (Rounded to 1,430)}}$$ 

(Actual loading on your carpet area = 43%) [4, 5, 6, 7, 8] 


## Why Do They Do This?


   1. Artificially Low Base Price: It allows the builder to market a lower "price per square foot" while collecting the exact same amount of money. [9] 

   2. Padding Common Areas: They shift the cost of grand entrance lobbies, wide corridors, and massive clubhouses directly onto your unit's invoice. [10, 11] 


## What Does the Law Say?

Under the Real Estate Regulatory Authority (RERA) guidelines in Hyderabad, builders are legally mandated to disclose and sell properties based strictly on Carpet Area. [12, 13] 

However, many private developers circumvent this by quoting a lower per-square-foot price on the Super Built-up Area rather than a higher per-square-foot price on the pure Carpet Area. If you look at your draft sale agreement, the exact carpet area must be written explicitly. [14, 15, 16] 


Wednesday, January 28, 2026

how to export certificate in pem format | SSL / TLS issues.

For TLS implementation in EBS it support PEM format.  

    Exporting a certificate in PEM format depends on your current file type (e.g., .pfx, .cer, .der) or the tool you are using. 
    1. Using OpenSSL (Cross-Platform)
    OpenSSL is the most common tool for converting certificates. 
    • From PFX (.p12 / .pfx): To export the certificate and private key together:
      openssl pkcs12 -in certificate.pfx -out certificate.pem -nodes
    • From DER (.cer / .der): To convert a binary DER file to a text PEM file:
      openssl x509 -inform der -in certificate.cer -out certificate.pem
    • From P7B (.p7b): To convert a PKCS#7 file:
      openssl pkcs7 -print_certs -in certificate.p7b -out certificate.pem
       
    2. Using Windows Certificate Export Wizard
    If the certificate is already installed on your Windows system:
    1. Open certmgr.msc (User) or certlm.msc (Local Computer).
    2. Right-click your certificate → All Tasks → Export.
    3. Select Base-64 encoded X.509 (.CER). This format is functionally identical to PEM.
    4. Complete the wizard and save the file. You can manually rename the extension from .cer to .pem if required by your application. 
    5. 3. Using a Web Browser
      To export a certificate from a website:
      • Chrome/Edge: Click the Padlock icon → Connection is secure → Certificate is valid → Details → Export. Choose Base-64 encoded X.509 or PEM if available.
      • Firefox: Click the Padlock → Connection secure → More Information → View Certificate → Details → Export. 
      4. Manual Creation (Combining Files)
      If you have separate .crt and .key files and need a single .pem file:
      1. Open a text editor like Notepad.
      2. Paste the contents of the certificate (including -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----).
      3. Paste the contents of the private key immediately below it.
      4. Save the file with a .pem extension.

Monday, September 8, 2025

ewallet p12 vs cwallet sso

The ewallet.p12 stores credentials and certificates protected by a user password, while cwallet.sso provides an obfuscated, random password for auto-login capabilities, allowing for passwordless wallet access. Both files are often used together in an Oracle auto-login wallet, where ewallet.p12 holds the sensitive data and cwallet.sso enables the wallet to open without requiring the user's password. 
Key Differences
  • ewallet.p12
    • Function: Stores private keys, certificates, and credentials. 
    • Protection: Protected by a user-defined password, which is required to access and modify the wallet. 
    • Use Case: For password-protected wallets where the password is provided during connection or modification. 
  • cwallet.sso
    • Function: Enables "auto-login" functionality, allowing for passwordless access to the wallet. 
    • Protection: Uses an obfuscated, random password that is more secure than a simple user password for auto-login. 
    • Use Case: Bound to the specific host and user where it was created for increased security in auto-login environments. 
Relationship in an Auto-Login Wallet
  • When you create an auto-login wallet using Oracle utilities, both ewallet.p12 and cwallet.sso files are generated. 
  • The ewallet.p12 file contains the essential credentials and certificates, while the cwallet.sso file contains the obfuscated password needed for the auto-login feature to work. 
  • The orapki utility can be used to modify the wallet, but it requires the wallet's original password, which was used to create the ewallet.p12 file. 

In summary: Use ewallet.p12 when you need a password-protected wallet to store your security credentials and certificates, and use cwallet.sso when you need the wallet to open automatically and bypass password prompts on the host it was created on. 

Friday, August 22, 2025

fnd concurrent request queues and logs update

 

create table apps.fnd_concurrent_queues_oci as select * from apps.fnd_concurrent_queues;
create table fnd_concurrent_requests_oci as select * from fnd_concurrent_requests;
create table xxau_fnd_concurrent_requests_oci as select * from xxau_fnd_concurrent_requests;
create table fnd_conc_req_outputs_oci as select * from apps.fnd_conc_req_outputs;

select CONCURRENT_QUEUE_NAME,NODE_NAME,NODE_NAME2,target_node from fnd_concurrent_queues_oci ;
select CONCURRENT_QUEUE_NAME,NODE_NAME,NODE_NAME2,target_node from fnd_concurrent_queues ;


select 'update fnd_concurrent_queues set node_name='''||NODE_NAME||''',NODE_NAME2='''||NODE_NAME2||''',TARGET_NODE='''||TARGET_NODE||''' where CONCURRENT_QUEUE_NAME ='''||CONCURRENT_QUEUE_NAME||''';' from fnd_concurrent_queues_oci;

 

col CONCURRENT_QUEUE_NAME for a20
set pages 500 lines 500
col 'Target_Node' for a20
col 'Node_Name' for a20
col 'Node_name2' for a20
select CONCURRENT_QUEUE_NAME,NODE_NAME,NODE_NAME2,target_node from fnd_concurrent_queues;
select CONCURRENT_QUEUE_NAME,TARGET_NODE,NODE_NAME,NODE_NAME2,RUNNING_PROCESSES,PCP_FLAG from fnd_concurrent_queues;
select CONCURRENT_QUEUE_NAME,TARGET_NODE,NODE_NAME,NODE_NAME2,RUNNING_PROCESSES,PCP_FLAG from fnd_concurrent_queues where target_node is not null;

update fnd_concurrent_queues set node_name='ASBAVEBSPRD17',NODE_NAME2='ASBAVEBSPRD18',TARGET_NODE='ASBAVEBSPRD17' where CONCURRENT_QUEUE_NAME in ( 'FNDICM','STANDARD','PASMGR','INVMGR','MRPMGR','WFALSNRSVC','WFMLRSVC','XDP_MANAGER','IEU_WL_CS','OKCCONCMGR','IEXCONMGR','OAMCOLMGR','WFWSSVC','FNDCPOPP','IEU_SH_CS','WFMGSMS','WFMGSMD','WMSTAMGR','CMICRM','FTE_TXN_MANAGER','AMSDMIN','FNDCRM','FNDSCH','PODAMGR','RCVOLTM','INVTMRPM','CRPINQMGR');

update fnd_concurrent_queues set node_name='ASBAVEBSPRD18',NODE_NAME2='ASBAVEBSPRD17',TARGET_NODE='ASBAVEBSPRD18' where CONCURRENT_QUEUE_NAME in ( 'XX_AU_MGR','XXSTD_ASC_DBMSPIPE');
Commit;


select CONCURRENT_QUEUE_NAME, CONTROL_CODE , TARGET_NODE, NODE_NAME,NODE_NAME2   from FND_CONCURRENT_QUEUES where concurrent_queue_name like 'XX_AU_MGR%';


select CONCURRENT_QUEUE_NAME,TARGET_NODE,NODE_NAME,NODE_NAME2,RUNNING_PROCESSES,PCP_FLAG from fnd_concurrent_queues where target_node is not null;


select distinct(TARGET_NODE)from fnd_concurrent_queues where target_node is not null;
select distinct(NODE_NAME)from fnd_concurrent_queues where target_node is not null;
select distinct(NODE_NAME2)from fnd_concurrent_queues where target_node is not null;

update fnd_concurrent_queues set target_node='ASBAVEBSPRD17' where target_node='IRXVLP0628';
update fnd_concurrent_queues set node_name='ASBAVEBSPRD17' where node_name='IRXVLP0628';
update fnd_concurrent_queues set node_name2='ASBAVEBSPRD17' where node_name2='IRXVLP0628';
 
update fnd_concurrent_queues set target_node='ASBAVEBSPRD18' where target_node='IRXVLP0629';
update fnd_concurrent_queues set node_name='ASBAVEBSPRD18' where node_name='IRXVLP0629';
update fnd_concurrent_queues set node_name2='ASBAVEBSPRD18' where node_name2='IRXVLP0629';
 
select distinct(logfile_node_name) from fnd_concurrent_requests; 
LOGFILE_NODE_NAME
----------------------------------------------------------------------------------------------------
ASBAVEBSDEV04
ASBAVEBSDEV03
ASBAVEBSI1B04
ASBAVEBSI1B03
IRXVLP0628
IRXVLP0629


select distinct(outfile_node_name) from fnd_concurrent_requests;
select distinct(logfile_node_name) from fnd_concurrent_requests;
select distinct(NODE_NAME1) from fnd_concurrent_requests;
select distinct(NODE_NAME2) from fnd_concurrent_requests;

update fnd_concurrent_requests set logfile_node_name='ASBAVEBSPRD17' where logfile_node_name='IRXVLP0628';
update fnd_concurrent_requests set logfile_node_name='ASBAVEBSPRD18' where logfile_node_name='IRXVLP0629';
update fnd_concurrent_requests set outfile_node_name='ASBAVEBSPRD17' where outfile_node_name='IRXVLP0628';
update fnd_concurrent_requests set outfile_node_name='ASBAVEBSPRD18' where outfile_node_name='IRXVLP0629';
update fnd_concurrent_requests set NODE_NAME1='ASBAVEBSPRD17' where NODE_NAME1 in ('IRXVLP0628');
update fnd_concurrent_requests set NODE_NAME1='ASBAVEBSPRD18' where NODE_NAME1 in ('IRXVLP0629');

commit;




Thursday, July 11, 2024

Execute Curl Utility to transfer tar file to Object Storage

Command to Upload Backup to Object Storage For OEL 5.8 the wget&curl TSLV is disabled please use Java option curl -X PUT -T / -u ‘@miracle.com:’ https://swiftobjectstorage.us-.miracleecloud.com/v1/// -x omcs-proxy.miracleoutsourcing.com:80 or java -jar uploadcli.jar -url https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/ -user fist.lastname@miracle.com -container .tar.gz

Tuesday, March 19, 2024

Important 12.2 Documents

10 References

This section lists the reference material that can be read to gain further knowledge in the various areas relevant to establishing a Maximum Availability Architecture for Oracle E-Business Suite, including the materials referenced to develop the processes described in this paper.

Database MAA:

Oracle Database High Availability Overview and Best Practices

Automatic Storage Management Administrator's Guide

Database Backup and Recovery User's Guide

 “Oracle Flashback Technology” in Oracle Database Concepts

Flashback Database Best Practices & Performance (Doc ID 565535.1)

“Using Edition Based Redefinition” in the Database Development Guide

Database Oracle Data Guard:

Data Guard Concepts and Administration

Data Guard Broker

Creating a Physical Standby using RMAN Duplicate (RAC or Non-RAC) (Doc ID 1617946.1)

Using Active Data Guard Reporting with Oracle E-Business Suite Release 12.2 and Oracle Database 19c (Doc ID 2608030.1)

Oracle Patch Assurance - Data Guard Standby-First Patch Apply (Doc ID 1265700.1)

Oracle Real Application Clusters (RAC):

Real Application Clusters Administration and Deployment Guide

Clusterware Administration and Deployment Guide

Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.2 (Doc ID 2530665.1)

Oracle RAC Rolling Install Process for the “Oracle JavaVM Component Database PSU” (OJVM PSU) Patches (Doc ID 2217053.1)

Oracle E-Business Suite MAA:

Business Continuity for Oracle E-Business Suite Release 12.2 on Oracle Database 19c Using Logical Host Names (Doc ID 2617788.1)

Oracle E-Business Suite on Exadata Database Machine (White Paper)

Oracle Site Guard

Oracle E-Business Suite Parallel Concurrent Manager:

Configuring and Managing Oracle E-Business Suite Release 12.2.x Forms and Concurrent Processing for Oracle RAC (Doc ID 2029173.1)

How to Activate Parallel Concurrent Processing - Background Facts and Setup Steps (Doc ID 602899.1)

Concurrent Processing - Parallel Concurrent Processing Failover/Failback Expectations (Doc ID 271090.1)

Managing Concurrent Manager Log and Out Directories (Doc ID 1616827.1)

Concurrent Processing - Purge Concurrent Request and/or Manager Data Program (FNDCPPUR) (Doc ID 104282.1)

Concurrent Processing - Best Practices for Performance for Concurrent Managers in E-Business Suite (Doc ID 1057802.1)

Concurrent Processing - Product Information Center (PIC) (Doc ID 1304305.1)

Oracle E-Business Suite Configuration and Management:

Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)

Can The Primary Node Hosting the WLS Admin Server Failover To A 12.2 Slave Node, Migrating the Master WLS Admin Server To Another Machine (Doc ID 1986122.1)

Oracle Applications E-Business Suite 12.2 Fusion Middleware Log Files: Locate, View, and Control (Doc ID 1366187.1)

Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release 12.2 (Doc ID 1905593.1)

HTTP Server Is Either Slow Or Stops Responding When Installed On A NFS Mounted Drive [Doc ID 560853.1]

Using Load-Balancers with Oracle E-Business Suite Release 12.0 and 12.1 (Doc ID 380489.1)

E-Business Suite 12.2 Detailed Steps To Change The R12.2 Default Port To 80 (Doc ID 2072420.1)

How to Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) (Doc ID 437260.1)

Secure Configuration Guide for Oracle E-Business Suite Release 12 (Doc ID 403537.1)

R12.2 : How To Create, Update or Rebuild The Central Inventory For Oracle Applications E-Business Suite ? (Doc ID 1588609.1)

How to Create a Clean oraInventory in Release 12.2 (Doc ID 1967205.1)

Best Practices for Gathering Statistics with Oracle E-Business Suite (Doc ID 1586374.1)

Fixed Objects Statistics Considerations [Doc ID 798257.1]

Sharing the Application Tier File System in Oracle E-Business Suite Release 12.2 (Doc ID 1375769.1)

Cloning Oracle E-Business Suite:

Cloning Oracle E-Business Suite Release 12.2 RAC Enabled Systems with Rapid Clone (Doc ID 1679270.1)

Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID 1383621.1)

Oracle E-Business Suite Application Tier Patching:

Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)

Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for R12.AD.C.Delta.9 and R12.TXK.C.Delta.9 (Doc ID 2233485.1)

12.2 Online Patching Utility ADOP Fails During Cutover Due to Error "[UNEXPECTED] adop has detected a configured disaster recovery site" (Doc ID 2131833.1)

The adop Patch Utility in the E-Business Suite Maintenance Guide

Oracle E-Business Suite Applications DBA and Technology Stack Release Notes for R12.AD.C.Delta.7 and R12.TXK.C.Delta.7 (Doc ID 2033780.1)

OPMN Fails to Start and Says to Check Adopmnctl.txt (Doc ID 2174221.1)

Oracle Engineered Systems (Exadata, SuperCluster):

Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID 888828.1)

Oracle Exadata Database Machine exachk or HealthCheck (Doc ID 1070954.1)

Oracle Exadata Best Practices (Doc ID 757552.1)

Database Patches Required by Oracle E-Business Suite on Oracle Engineered Systems: Exadata Database Machines and SuperClusters (Doc ID 1392527.1)

Exadata Write-Back Flash Cache - FAQ (Doc ID 1500257.1)

Oracle Exadata Database Machine Performance Best Practices (Doc ID 1274475.1)

Configuring Exadata I/O Resource Manager for Common Scenarios (Doc ID 1363188.1)

Oracle Exadata Database Machine Setup/Configuration Best Practices (Doc ID 1274318.1)

Oracle SuperCluster Supported Software Versions – All Hardware Types (Doc ID 1567979.1)

OS Required Packages and HugePages:

Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)

HugePages on Oracle Linux 64-bit (Doc ID 361468.1)

HugePages and Oracle Database 11g Automatic Memory Management (AMM) on Linux (Doc ID 749851.1)

USE_LARGE_PAGES To Enable HugePages (Doc ID 1392497.1)

Real estate builders fraud

 actual carpet area 1000sft and common area 30%  it should be 1300 but builder  sell it as 1430 sft saying 30% common area.  where as they a...