Wednesday, 16 December 2015

R12: Concurrent Manager extra log errors  start apps/apps diag=Y

Check log file  $LOG_HOME/appl/conc/log/*.mgr 

Saturday, 12 December 2015 exiting with status 150

If,, not coming up after start the application services exiting with status 150 exiting with status 150 exiting with status 150

Check the log file for these three processes:
If you see error like below

opmn id=server291:6219
    no processes or applications matched this request

12/13/15-08:16:46 :: exiting with status 150

Stop all three services.
Clean the directory, under  persistence from below directory and restart all three services
rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/*
rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/*
rm -rf $ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence/*

Saturday, 5 December 2015

MSSQL Server orphaned user issue/resolution

alter user username with login=[username]

Friday, 13 November 2015

While install Oracle Database 11g Error in starting the service. The service OracleMTSRecoveryService was not found

Keep the popup and move to:
Regedit > hkey_local_machine\system\controlset001\service\OracleMTSRecoveryService

In the ImagePath key, change the path to your actual home path. 

Saturday, 7 November 2015 failure while running Oracle clusterware installation

If the fails on a node and you try to re execute it after fixing the failure then it gives the following error:

CRS is already configured on this node for crshome=0 Cannot configure two CRS instances on the same cluster.Please deconfigure before proceeding with the configuration of new home.

In order to perform a cleanup you will need to execute the following two commands as the root user.
In all the nodes where the failed execute the following:
# perl $GRID_HOME/crs/install/ -verbose -deconfig -force

On the last node of the cluster execute the following as the root user:
# perl $GRID_HOME/crs/install/ -verbose -deconfig -force -lastnode

Now you will be in a state where you can re execute the command.

Wednesday, 4 November 2015

ORA-01653: unable to extend table SYS.AUD$

No body is able to connect :

ORA-00604: error occurred at recursive SQL level 1
ORA-01653: unable to extend table SYS.AUD$ by 8192 in tablespace SYSTEM
ORA-02002: error while writing to audit trail

server223[/home/oracle]>>sqlplus / as sysdba
SQL> truncate table aud$;

Table truncated.


Tuesday, 3 November 2015

ORA-29285: file write error

We were extracting some data into text file and then we noticed the above error. I checked many things, everything seemed ok. I realized that i get this error only for certain write operations when length of buffer was more than 1024. We had used following call to open file

UTL_FILE.fopen(, , 'w'); 

Since 4th parameter to UTL_FILE.fopen was not passed, it was defaulted to 1024. Hence the error when buffer was more than 1024.

Solution: we changed the call to UTL_FILE.fopen and passed 4th parameter max_linesize as 32767.

Number of Visitors