Sunday, October 18, 2009

Couldn't open ICX Application Message file

One off my team mate reported an issue while opening forms in Purchasing Super user he encountered error message:
"Message Dictionary couldn't open the ICX application message file. Cannot open file /u02/apps/apps_st/appl/icx/12.0.0/mesg/US.msb for reading."

When I checked the location it was not there. Then I though running generate message file from adadmin but it didn't help. Here is the solution :

We have run Concurrent request "Generate Messages" for "Oracle iProcurement" and it will generate US.msb file under required location.

Happy Troubleshooting !!!

R12 New features

While using R12 I come across few things which might help you guys too:

1. It doesn't require to change apps password in any config files. So no need to run autoconfig if you used to do it.
2. All startup files are in $INST_TOP/admin/scripts
3. While creating Share Appl Top we can keep all other tops as read only except INST_TOP.
4. While running $INST_TOP/admin/scripts/ it require apps password only. No need to provide Context file location any more.
5. CONTEXT File location is $INST_TOP/appl/admin
6. If you want to install R12 on virtual host start rapidwiz as "rapidwiz -servername virtual"
7. Just change s_cphost to physical hostname and run autoconfig, otherwise ICM and WF Mailer container components will have issue while starting.

I will keep on posting stuff as and when I come across. Till then

Happy Trobleshooting !!!

How to change Oracle user ORACLE_HOME

We have to change our ora user $ORACLE_HOME from /u02/oracle to /u02/oracle/11.1.0. Here are steps which I have followed and done this.

1. Run on dbtier as oracle user
perl dbTier
2. Shutdown down database and listener.
3. mv all files from /u02/oracle to /u02/oracle/11.1.0
4. run for binaries only to avoid db creation
perl dbTechStack
It will ask you certain info, please provide it accordingly.
5. update profiles from $OH/appsutil/install/
sqlplus "/ as sysdba" @adupdlib.sql so
6. change directory to $OH/appsutil/clone/bin
perl dbconfig $OH/appsutil/context_file.xml
7. run autoconfig on appstiers too.
8. Start all services and check.

Happy Troubleshooting !!!

MWA server in R12

If you are suppose to run MWA server in R12 you might feel like something is missing here from 11i. So just read it and you will be able to handle it.
Prior to R12:
1. The MWA server startup files were located under "$MWA_TOP/bin" directory.
2. The MWA Server configuration files were located under "$MWA_TOP/secure" directory.
In R12
1. Scripts are under $INST_TOP/admin/scripts
2. Config files are under $INST_TOP/admin/install

Here are few commands and which we used to use in 11i, this is how we are going to use them in R12:
1. Startup the MWA server start
2. Shutdown the MWA server -login adminuid/pwd stop_force
3. Startup MWA Dispatcher start_dispatcher
4. Shutdown MWA Dispatcher stop_dispatcher

By default these scripts were not included in and scripts. To add them enable
1. s_other_service_group_status
2. s_mwastatus
in context file and run autoconfig.

If you want to check port number for mwa. Look at following paramters in context file:
1. s_mwaPortNo.
2. s_mwaTelnetPortNo.

Happy Troubleshooting !!!

Rename Temp datafiles in 11G

Sorry all its big gap I took to post any update here. Biggest problem is office security. Now I can't access my blog site from office network. So I have to wait till I get some time at home. And as you might know this is festival season here in India to took so long. Any ways come to the point. Recently we have installed R 12.1.1 fresh installation on solaris and had to change many things after install. Temp datafiles location is one of them. But I got confused initially. Becuase when I was checking tablespace_name, file_name from dba_temp_files, I was getting TEMP1 and TEMP2 as tablespace names. But when I checked temporary_tablespace in dba_users I saw it as TEMP. So was worried how come? where is the link between these two miss matched things. Temporary Tablespace Group were the cause for it. Or I would say solution for this.
Here is the brief information about them:
1. A temporary tablespace group must consist of at least one tablespace. There is no explicit max number of tablespaces.
2. If you delete all members from a TTG, the group is automatically deleted as well.
3. When you assign a temporary tablespace to a user, you can use the TTG name instead of the actual temporary tablespace name. you can also use the TTG name when you assign the default temporary tablespace for the database.

This is how we can create one TTG;
1. Create Temporary Tablespace temp1 tempfile '/u02/oracle/temp1_01.dbf' size 100M tablespace group temp;
2. Add more via : Alter tablespace temp2 tablespace group temp;
3. Setting group as default temporary tablespace for the database:
Alter database Default Temporary Tablespace Temp;
4. Query dba_tablespace_groups for information about them.

Now coming to our topic how to rename tempfiles:
1. Create another temp tablespace to make it default.
Create Temporary Tablepspace temp_sd tempfile '/u02/oracle/temp/temp_sd_01.dbf' size 2000M;
2. Make this as default Temp Tablespace:
Alter database default temporary tablespace temp_sd;
3. Check database properties to be sure:
Select property_name, property_value from database_properties where property_name like '%Default_TEMP_TABLESPACE%';
4. Alter database tempfile '/u02/oracle/temp01.dbf' offline;
5. Copy file from old location to new location using OS commands.
cp /u02/oracle/temp01.dbf /u02/oracle/temp/temp01.dbf
6. Rename file
Alter database rename file '/u02/oracle/temp01.dbf' to '/u02/oracle/temp/temp01.dbf';
7. Bring it online
Alter database tempfile '/u02/oracle/temp/temp01.dbf' online;
8. Again change the default:
Alter database default temporary tablespace temp;
9. Drop the newly create temp tablespace
Drop Tablespace temp_sd including contents and datafiles;

Happy Troubleshooting !!!
Happy Diwali !!!