Usage of DB_FILE_NAME_CONVERT

By
 DB_FILE_NAME_CONVERT = 'string1' , 'string2' , 'string3' , 'string4' , ...

Where:

  • string1 is the pattern of the primary database filename

  • string2 is the pattern of the standby database filename

  • string3 is the pattern of the primary database filename

  • string4 is the pattern of the standby database filename

You can use as many pairs of primary and standby replacement strings as required. You can use single or double quotation marks.

The following are example settings that are acceptable:

DB_FILE_NAME_CONVERT = '/dbs/t1/','/dbs/t1/s_','dbs/t2/ ','dbs/t2/s_'


DB_FILE_NAME_CONVERT is useful for creating a duplicate database for recovery purposes. It converts the filename of a new datafile on the primary database to a filename on the standby database. If you add a datafile to the primary database, you must add a corresponding file to the standby database. When the standby database is updated, this parameter converts the datafile name on the primary database to the datafile name on the standby database. The file on the standby database must exist and be writable, or the recovery process will halt with an error.


*.db_file_name_convert='/apptrngrt/product/oradata/CDBEBSDV','/ordascn7i/product/oradata/CDBEBSDV'

*.log_file_name_convert='/apptrngrt/product/oradata/CDBEBSDV','/ordascn7i/product/oradata/CDBEBSDV'

Comments

Post a Comment

Popular posts from this blog

End of Support date for Oracle WebLogic Server

By
  WebLogic Server 12.1.x Releases Version Release Date Announcement End of Grace Period WLS 12.1.1.0.0 Dec-11 n/a JUL 2015 (b) FMW 12.1.2.0.0 Jul-13 Note 1567707.1 JUN 2016 (b) FMW 12.1.3.0.0 Jun-14 Note 1567707.1 (a)(b)(c)   (a) End of Error Correction is determined by a subsequent Patch Set release to set the beginning of the grace period. Without a subsequent Patch Set release, this version has error correction support as per the Lifetime Support Policy document’s Premier and Extended Support dates. Look for “12.1.x”. (b) For 12c Release 1 (12.1), the grace period date is set based on the third digit or minor version, (e.g., 12.1.1, 12.1.2, 12.1.3) with a two year grace period for these 12.1.x releases. No Patch Sets were released for WebLogic Server 12.1.x. For WLS 12.1.x, the grace period date is set based on the third digit or minor version, e.g., 12.1.1, 12.1.2, 12.1.3. See Error Correction Policy Note 209768.1 and look for Oracle Fusion Middleware Appendix A.2. (c) Upd...
Read more

How to set up the Oracle Wallets in Oracle Database 19C

By
  The Oracle Wallet is a container or repository that stores authentication and credentials such as certificates, certificate requests, and private keys., By using this we can connect to database without providing the schema name & password, Password will be connected by using the TNS ALIES name & hence the schema are encrypted & stored in the oracle wallets. Let us configure the schema password by using the wallets. Create a directory to store the wallets. Create a directory to store the password $ mkdir -p /u01/app/wallets Create a wallet & provide the wallet password. $ mkstore -wrl /u01/app/wallets/ -create Enter password: ********* Enter password again: ******** $ ll total 8 -rw-------. 1 oracle oinstall 194 Nov 1 14:38 cwallet.sso -rw-------. 1 oracle oinstall 0 Nov 1 14:38 cwallet.sso.lck -rw-------. 1 oracle oinstall 149 Nov 1 14:38 ewallet.p12 -rw-------. 1 oracle oinstall 0 Nov 1 14:38 ewallet.p12.lck Check the status of listener $lsnrctl status listener_n...
Read more

How to drop index and before dropping it how to get the DDL.

By
  Oracle DROP INDEX statement DROP INDEX [schema_name.]index_name; DECLARE index_count INTEGER; BEGIN SELECT COUNT(*) INTO index_count FROM USER_INDEXES WHERE INDEX_NAME = 'index_name' ; IF index_count > 0 THEN EXECUTE IMMEDIATE 'DROP INDEX index_name' ; END IF; END; / In case want to check whether index exists and then delete it. If try to drop a non-existing, you will get the following error: SQL Error : ORA -01418 : specified index does not exist In SQLplus, set these before running the commands set long 100000 set longchunksize 100000 select DBMS_METADATA.GET_DDL( 'INDEX' , 'index_name') from all_indexes where owner in ( USER , 'USER_OTHER_THAN_LOGGED_IN_USER' ); Use below script to fetch metadata other information. SELECT DBMS_METADATA,GET_GRANTED_DDL('SYSTEM_GRANT','SSO******') from dual;
Read more

How to use JPXImporter in EBS12.2

By
  java   oracle.jrad.tools.xml.importer.JPXImporter   $HOME/kturley/ XXCUST_projects_list.jpx   -username apps -password xxxx -dbconnection “(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST= hostname.oracle.co.uk)(PORT=1551))(CONNECT_DATA=(SID=XXXXX )))”  Make sure you specify the correct values for  1. Path of you jpx file  2. apps password  3. host name  4. port  5. database SID  Finally restart the webserver so that you can see your changes in the application  $INST_TOP/admin/scripts/ adoacorectl.sh  stop $INST_TOP/admin/scripts/ adoacorectl.sh  start  
Read more

Change Password in an Oracle Database

By
 Once connected, ALTER USER command, specifying the new password. ALTER USER myuser IDENTIFIED BY MyNewPassword; To use special characters, remember to enclose the password in double quotes. ALTER USER myuser IDENTIFIED BY "MyNewPassword#"; SQL*Plus and SQLcl Use the PASSWORD command from the SQL*Plus and SQLcl utilities. It will be prompted for your current password and the new password. SQL> password Changing password for MYUSER Old password: ******** New password: ******** Retype new password: ******** Password changed SQL> SQL Developer From SQL Developer Right-click on the connection. Select the "Reset Password..." option from the popup menu. In the subsequent dialog, enter the current password and the new password with confirmation. Click the OK button. TOAD For TOAD do the following. select "Session > Change Password". In the subsequent dialog, enter the current password and the new password with verification. Click the OK button.
Read more
By
Can I flush the Undo tablespace by any chance... ? You don't need to flush any thing from the undo tablespace. It will reuse the undo data automatically. You can create a new undo tablespace and make it active for your database. Later on drop your old undo tablespace. UNDO_RETENTION time undo tablespace is filled and any query fails, then if another query is going to do a DML and tries to use UNDO segments then, I think that will also fail because of unavailability of UNDO SEGMENTS.. > create undo tablespace undotbl_new datafile size 1m; Tablespace created. > alter system set undo_tablespace = undotbl_new scope=both; System altered. > drop tablespace undotbs; Tablespace dropped.
Read more

Get FND Profile Values in Oracle EBS 12.2

By
SELECT FND_PROFILE.VALUE (‘MFG_ORGANIZATION_ID’), FND_PROFILE.VALUE (‘ORG_ID’), FND_PROFILE.VALUE (‘LOGIN_ID’), FND_PROFILE.VALUE (‘USER_ID’), FND_PROFILE.VALUE (‘USERNAME’), FND_PROFILE.VALUE (‘CONCURRENT_REQUEST_ID’), FND_PROFILE.VALUE (‘GL_SET_OF_BKS_ID’), FND_PROFILE.VALUE (‘SO_ORGANIZATION_ID’), FND_PROFILE.VALUE (‘APPL_SHRT_NAME’), FND_PROFILE.VALUE (‘RESP_NAME’), FND_PROFILE.VALUE (‘RESP_ID’) FROM DUAL; FND_PROFILE.PUT Summary procedure FND_PROFILE.PUT (name IN varchar2, valueIN varchar2); Location FNDSQF library and database (stored procedure) Description Puts a value to the specified user profile option. If the option does not exist, you can also create it with PUT. All PUT operations are local -- in other words, a PUT on the server affects only the server-side profile cache, and a PUT on the client affects only the client-side cache. By using PUT, you destroy the synchrony between server-side and client-side profile caches. As a result, we do not recommen...
Read more

How to troubleshoot Output Post Processor Issues

By
  The Output Post Processor (OPP) is designed to support XML Publisher as a post-processing action for concurrent requests. If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output. Memory Usage Per Process: The maximum amount of memory or maximum Java heap size a single OPP process can use is by default set to 512MB. This value is needed by the Loader Data File: $FND_TOP/patch/115/import/US/afoppsrv.ldt which specifies that the DEVELOPER_PARAMETERS is “J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m”. How to determine the current Java heap size: SELECT service_id, service_handle, developer_parameters FROM fnd_cp_services WHERE service_id = (SELECT manager_type FROM fnd_concurrent_queues WHERE concurrent_queue_name = ‘FNDCPOPP’); Increase the maximum Java heap...
Read more

How to Check AD and TXK code levels in your EBS environment

By
Below query can be used in finding out current AD and TXK code levels.  [ap******@shsd*** 22989949]$ sqlplus apps SQL*Plus: Release 10.1.0.5.0 - Production on Fri Sep 30 01:00:25 2022 Copyright (c) 1982, 2005, Oracle.  All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production SQL> col ABBREVIATION for a10 set lines 1000 col NAME for a50 col CODELEVEL for a20 SELECT ABBREVIATION,NAME,codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad');SQL> SQL> SQL> SQL> ABBREVIATI NAME                                               CODELEVEL ---------- -------------------------------------------------- -------------------- ad         Oracle Applications DBA                            C.13 txk  ...
Read more

Verifying Daemon “Avahi-Daemon” Not Configured And Running …FAILED (PRVG-1360)

By
  Execute "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" as root user on nodes "shsebs7idb1" to perform the fix up operations manually Press ENTER key to continue after execution of "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" has completed on nodes "shsebs7idb1" Fix: Daemon "avahi-daemon" not configured and running   Node Name                             Status   ------------------------------------  ------------------------   shsebs7idb1                           failed ERROR: shsebs7idb1: PRVG-9023 : Manual fix up command "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" was not issued by root user on node "shsebs7idb1" Result: "Daemon "avahi-daemon" not configured and running" could not be fixed on nodes "shsebs7idb1" SOLUTION: To fix this error, stop and disable avahi-daemon service. 1. Check avahi-daemon status: [root@shsebs7idb1 ~]# ls -...
Read more