Developer Suite has been installed successfully on a MS Windows Vista system.To meet the MS Windows Vista certification this instructions were followed. On trying to open or to compile a reports module file (RDF) in Reports Builder, the Builder crashes.Opening a Forms module file (FMB) in the Forms Builder crashes the Builder.Error(s)Windows Vista complains there has been a problem in Reports Builder and is trying to work it out.But eventually, it states that Reports Builder is going to be closed.
This is because despite applying patchset 10.1.2.3 there are still issues in the 10.1.0.5 DB client causing the crashes.
Apply
Patch 7047034 ORACLE 10G 10.1.0.5 Patch 26 BUG FOR WINDOWS 32 BIT
to the ORACLE_HOME of the Developer Suite installation.
The patch can be downloaded from Metalink's PATCHES section doing a SIMPLE SEARCH for patch number 7047034 and platform MS Windows (32-bit).
Follow the instructions of the patch readme carefully.
Monday, August 31, 2009
Standard manager fails to start
A concurrent program that had its basepath defined wrong when it was registered was submitted. which caused the standard manager to crash. and since the concurrent program was in the standard manager queue, the manager would crash as soon as the concurrent managers are restarted since the program is executed as soon as the concurrent managers are online. None of the log files reported any error except in the manager log of the deactivated processes ( of the standard manager) in the front end. all of the deactivated processes log's contained the request ID of the concurrent program.
The solution was to remove the concurrent program from the queue and correct the basepath of the concurrent program under the system administrator -> applications -> register to the correct custom top path as in the OS level and restart the concurrent managers.
The solution was to remove the concurrent program from the queue and correct the basepath of the concurrent program under the system administrator -> applications -> register to the correct custom top path as in the OS level and restart the concurrent managers.
RMAN Restore and recovery scenarios
Test Case1:
1. Startup the database in nomount mode
sql> startup nomount
2. Restore the control file from the backup you want to restore
RMAN> set DBID=XXXXXXXXXX
RMAN> restore controlfile from '/backups/rman/ctlback'
3. Mount the database
SQL> startup mount;
4. Find out the max sequence of the archive file and restore max+1 as its an incomplete recovery,
You can find it either using RMAN or through SQL,
RMAN> list backup of archivelog all;
SQL> set serverout on;
SQL> set num 50;
SQL> select sequence#,NEXT_CHANGE# from v$archived_log order by next_change# desc;
5. Restore and recover the database upto the archive log we have,
RMAN>
run
{
set until sequence 2337;
restore database;
recover database;
sql 'alter database open resetlogs';
}
Test Case 2:
Move the datafile tx_data7.dbf to another name after shutting down the database
2. startup the database, you will get the following error
ORA-01113: file 33 needs media recovery
ORA-01110: data file 33: '/u01/oracle/visndata/tx_data7.dbf'
3. Offline the datafile and open the database
4. Restore it using RMAN as follows,
RMAN> restore datafile 44;
or
SQL> alter database datafile '/u01/oracle/visndata/tx_data7.dbf' online;
alter database datafile '/u01/oracle/visndata/tx_data7.dbf' online
*
ERROR at line 1:
ORA-01113: file 33 needs media recovery
ORA-01110: data file 33: '/u01/oracle/visndata/tx_data7.dbf'
SQL>
SQL> recover datafile '/u01/oracle/visndata/tx_data7.dbf';
Media recovery complete.
SQL> alter database datafile '/u01/oracle/visndata/tx_data7.dbf' online;
Database altered.
Test Case: 3
Restore of datafiles from a full hot backup and complete recovery
RMAN offline or online database backup
Target database mode: Archivelog
Loss: All current datafiles have been lost. Current controlfiles and redo logs are still available.
Requirement: Restore and complete recovery
This example simulates the loss of the current database datafiles.
The current controlfile and redo logs are still intact.
Target database mode: Database mounted
RMAN> run {
restore database;
recover database;
sql "alter database open";
}
Notes:
Archived logs will be restored automatically as required.It is possible, but not necessary, to manually restore from an archivelog backupset
Test Case: 4
Restore of datafiles from a full hot backup and complete recovery
RMAN offline or online database backup
Target database mode: Archivelog
Loss: All current datafiles have been lost, current and inactive redolog groups member has been lost, controlfiles are also lost
Requirement: Restore and complete recovery of control files and open the database with resetlogs
select FIRST_CHANGE#,sequence# from v$archived_log order by FIRST_CHANGE# desc;
In our example we restored the control file from an incremental backup, but the latest archive log sequence is 70 and which is available on the disk, so in order for a complete recovery we need
RMAN> catalog archivelog '/u01/arch/NGIND_arch_70_1_672703990.arc';
cataloged archive log
archive log filename=/u01/arch/NGIND_arch_70_1_672703990.arc recid=4 stamp=678426497
Target database mode: Database mounted
RMAN> list archivelog all;
RMAN> run {
restore database;
recover database;
sql "alter database open resetlogs";
}
Notes:
Archived logs will be restored automatically as required if they are cataloged.It is possible, but not necessary, to manually restore from an archivelog backupset
Test Case: 5
Restore of datafiles from a full hot backup and complete recovery
RMAN offline or online database backup
Target database mode: Archivelog
Loss: All current datafiles have been lost, inactive and one current redo log is lost, current file is still available
Requirement: Restore and complete recovery of control files and open the database with resetlogs
RMAN> run {
restore database;
recover database;
sql "alter database open resetlogs";
}
Notes:
Archived logs will be restored automatically as required if they are cataloged.It is possible, but not necessary, to manually restore from an archivelog backupset
How To Relink A Single Executable Via ADADMIN
How to regenerate a single executable using ADADMIN utility?
1. Run adadmin and answer the standard startup questions; see Oracle Applications Maintenance Utilities Release 11i 11.5.10 (Part No. B13586-01): "Running AD Utilities". At the AD Administration Main Menu select the option: Maintain Applications Files menu
2. At the Maintain Applications Files menu select the option: Relink Applications programs
3. At the prompt "Do you wish to proceed with the relink [Yes] ?" Hit return for the default option.
4. At the prompt "Enter the name of your Oracle Applications environment file below. File name [*.env] : " Hit return for the default option or correct the file if necessary.
5. At the prompt "Enter list of products to link ('all' for all products) [all] :" enter the product's short name associated with the target executable, such as "fnd".
6. At the prompt "Generate specific executables for each selected product [No] ?" enter Yes
7. At the prompt "Relink with debug information [No] ?" Hit return for the default option.
8. At the prompt "Enter executables to relink, or enter 'all' [all] :" the exact name of the executable to be relinked.
1. Run adadmin and answer the standard startup questions; see Oracle Applications Maintenance Utilities Release 11i 11.5.10 (Part No. B13586-01): "Running AD Utilities". At the AD Administration Main Menu select the option: Maintain Applications Files menu
2. At the Maintain Applications Files menu select the option: Relink Applications programs
3. At the prompt "Do you wish to proceed with the relink [Yes] ?" Hit return for the default option.
4. At the prompt "Enter the name of your Oracle Applications environment file below. File name [*.env] : " Hit return for the default option or correct the file if necessary.
5. At the prompt "Enter list of products to link ('all' for all products) [all] :" enter the product's short name associated with the target executable, such as "fnd".
6. At the prompt "Generate specific executables for each selected product [No] ?" enter Yes
7. At the prompt "Relink with debug information [No] ?" Hit return for the default option.
8. At the prompt "Enter executables to relink, or enter 'all' [all] :" the exact name of the executable to be relinked.
How to uninstall backout rollback an Oracle Applications 11i Patch
How to backout rollback an Oracle Applications 11i Patch
There is no automated method of backing out patches.
This can be a really complex operation which depends on the patch complexity and sometime the mostreasonable suggestion is to restore from a backup.
Main Advices :
- In all cases before applying a large number of patches, a series of mini-packs, family packs, ora maintenance pack, back up the Oracle Applications file system and database.
- You should always test the application of a patch several times on a test system, particularlyif the patch is a mini-pack, family pack, or maintenance pack. Once the test application issuccessful, apply the patch on the production system.
- Determine the cause of the failure.In many cases, the issue can be resolved and the patching process restarted at the point of failure.
If you are not able to solve the issue for the patch application, you have to consider 2 cases :
- Backing out the files from the APPL_TOP
- Backing out the Database actions
There is no automated method of backing out patches.
This can be a really complex operation which depends on the patch complexity and sometime the mostreasonable suggestion is to restore from a backup.
Main Advices :
- In all cases before applying a large number of patches, a series of mini-packs, family packs, ora maintenance pack, back up the Oracle Applications file system and database.
- You should always test the application of a patch several times on a test system, particularlyif the patch is a mini-pack, family pack, or maintenance pack. Once the test application issuccessful, apply the patch on the production system.
- Determine the cause of the failure.In many cases, the issue can be resolved and the patching process restarted at the point of failure.
If you are not able to solve the issue for the patch application, you have to consider 2 cases :
- Backing out the files from the APPL_TOP
- Backing out the Database actions
How to Remove an Oracle Applications 11i node
How to remove an Oracle E-Business suite Apps tier node.
T0 remove a node requires the node is deregistered from the Net Services Topology Data Model in one of the following cases:
* To delete an application tier
* The Database is upgraded/migrated resulting in a change in one of the following parameters:
o Database Host
o Database Port
o Database Name
o Database SID
The tier should be deregistered before the tier is decommissioned.
How to deregister an application tier from the Net Services Topology Data Model?
To deregister the current application tier from the Net Sevices Topology Data Model, invoke the following command:
perl/bin/adgentns.pl appspass= contextfile= -removeserver
T0 remove a node requires the node is deregistered from the Net Services Topology Data Model in one of the following cases:
* To delete an application tier
* The Database is upgraded/migrated resulting in a change in one of the following parameters:
o Database Host
o Database Port
o Database Name
o Database SID
The tier should be deregistered before the tier is decommissioned.
How to deregister an application tier from the Net Services Topology Data Model?
To deregister the current application tier from the Net Sevices Topology Data Model, invoke the following command:
perl
How To Quick Solve This Post Clone Error : RC-50004, AC-00005: No write permissions for creating the Context file - /tmp/temp.xml ?
On R12 (or 11i) , while executing 'perl adcfgclone.pl', we are facing the error as following:
Target System Display [testerp:0.0] : RC-50004: Error occurred in CloneContext: AC-00005: No write permissions for creating the Context file - /tmp/temp.xml Raised by oracle.apps.ad.context.AppsContext Check Clone Context logfile /oracle/Test/Application/apps/apps_st/comn/clone/bin /CloneContext_06151127.log for details.
ERROR: Context creation not completed successfully. For additional details review the file /tmp/adcfgclone_4796.err if present.
Apps user does not have write permissions on /tmp directory.
1- Give write permission to apps user on "/tmp" directory.
Example :
As root:
# chmod 777 /tmp
# ls -al grep tmp
drwxrwxrwx 11 root root 4096 Jun 15 04:02 tmp
2- Re-run the Postclone.
perl adcfgclone.pl
Nb:
We could hit this Error too:
Following stacktrace produced when running adcfgclone.pl StackTrace: java.lang.Exception: AC-00005: No write permissions for creating the Context file - /u01/PROD/oracle/920/appsutil/temp.xml Raised by oracle.apps.ad.context.AppsContext at oracle.apps.ad.context.AppsContext. getOaEnabledValues(AppsContext.java:733) at oracle.apps.ad.context.CloneContext.doClone(CloneContext.java: 657) at oracle.apps.ad.context.CloneContext.main(CloneContext.java:6033) RC-50004: Error occurred in CloneContext: AC-00005: No write permissions for creating the Context file - /u01/PROD/oracle/920/appsutil/temp.xml Raised by oracle.apps.ad.context.AppsContext Context file creation not succesful
Analysis:
The error above is a bit misleading. adcfgclone.pl should not be creating a "temp.xml" file under appsutil, The context file created under "/u01/PROD/oracle/920/appsutil" should be
Normally adcfgclone.pl is trying to do is, create files under /usr/tmp and/or /tmp.
Check if you have a temp.xml file or other RapidClone files under either of those directories owned by a different user? If so please delete them and retry adcfgclone.pl.
Subscribe to:
Posts (Atom)