this message happens with database crash.
when a background process like DBW0 terminated abnormally, PMON will terminated the database.
the root cause need be found from alert log, trace file and etc.
Wednesday, February 1, 2012
Thursday, January 26, 2012
check datapump jobs
1. find job name
select * from user_datapump_jobs;
select * from dba_datapump_sessions;
2. login to datapump and attache the job
impdp attach=[schema].job_name
ATTEN: don't user hyphen - in you job name. You may not be able to attach to a job have hyphen in its name.
3.
impdp> status
reference:
http://peerdba.wordpress.com/2011/01/13/killing-expdpimpdp-job/
select * from user_datapump_jobs;
select * from dba_datapump_sessions;
2. login to datapump and attache the job
impdp attach=[schema].job_name
ATTEN: don't user hyphen - in you job name. You may not be able to attach to a job have hyphen in its name.
3.
impdp> status
reference:
http://peerdba.wordpress.com/2011/01/13/killing-expdpimpdp-job/
Wednesday, January 18, 2012
codepage setting informatica
1. the error you may get
LM_36011
Code page mismatch. Service process is running in code page [UTF-8 encoding of Unicode] whereas the service is configured in the Admin Console to run in code page [ISO 8859-1 Western European]
2. system variable used to set codepage
Use LANG and LC_ALL to set the UNIX code page for the installer.
Set the LANG and LC_ALL environment variables to the following values for the
language that you use:
- English: C
- Japanese: ja_JP.SJIS or ja_JP.PCK
- Portuguese: pt_BR.ISO8859-1, pt_BR.8859-15, or pt_BR
After you install, update the locale setting to one that is compatible with the code
page of the repository.
3. another vairable used to set codepage
INFA_CODEPAGENAME
4. there are three place you have code page set up
4.1 the informatica server process
4.2 the power center repository service
4.3 the power center integration service
5. the requirements is
5.1 both service must have superset or same of codepage as the server process
5.2 Repository service must have superset or same of codepage as the integration service.
6. situation cause the error
6.1 set INFA_CODEPAGENAME=UTF-8
repository = [UTF-8 encoding of Unicode]
integration = [ISO 8859-1 Western European]
6.2 repository = [ISO 8859-1 Western European]
integration = [UTF-8 encoding of Unicode]
if INFA_CODEPAGENAME is not set, default is [ISO 8859-1 Western European]
there are other situations,which may cause the error. It should be fixed after assign correct code page.
reference:
http://dbcrusade.blogspot.com/2009/06/informatica-setting-codepage.html
Informatica 9.0.1 administrator Guide
Power center 9.0.1 Hotfix 1 Installation and Configuration Guide
LM_36011
Code page mismatch. Service process is running in code page [UTF-8 encoding of Unicode] whereas the service is configured in the Admin Console to run in code page [ISO 8859-1 Western European]
2. system variable used to set codepage
Use LANG and LC_ALL to set the UNIX code page for the installer.
Set the LANG and LC_ALL environment variables to the following values for the
language that you use:
- English: C
- Japanese: ja_JP.SJIS or ja_JP.PCK
- Portuguese: pt_BR.ISO8859-1, pt_BR.8859-15, or pt_BR
After you install, update the locale setting to one that is compatible with the code
page of the repository.
3. another vairable used to set codepage
INFA_CODEPAGENAME
4. there are three place you have code page set up
4.1 the informatica server process
4.2 the power center repository service
4.3 the power center integration service
5. the requirements is
5.1 both service must have superset or same of codepage as the server process
5.2 Repository service must have superset or same of codepage as the integration service.
6. situation cause the error
6.1 set INFA_CODEPAGENAME=UTF-8
repository = [UTF-8 encoding of Unicode]
integration = [ISO 8859-1 Western European]
6.2 repository = [ISO 8859-1 Western European]
integration = [UTF-8 encoding of Unicode]
if INFA_CODEPAGENAME is not set, default is [ISO 8859-1 Western European]
there are other situations,which may cause the error. It should be fixed after assign correct code page.
reference:
http://dbcrusade.blogspot.com/2009/06/informatica-setting-codepage.html
Informatica 9.0.1 administrator Guide
Power center 9.0.1 Hotfix 1 Installation and Configuration Guide
ulimit - user limit set in linux
1. check your limitation
ulimit -a
ulimit -n (number of open file)
2. set new limitation temporarily
ulimit -n newvalue
3. set new limitation permenant
3.1 vi /etc/security/limits.conf
add
username - nofile 2048
3.2. sysctl -p
4. set limitation system-wide
4.1 vi /etc/sysctl.conf
4.2 sysctl -p
reference:
http://cherry.world.edoors.com/CPZKoGkpxfbQ
http://www.linuxquestions.org/questions/slackware-14/increasing-file-descriptors-228004/
http://www.xenoclast.org/doc/benchmark/HTTP-benchmarking-HOWTO/node7.html
ulimit -a
ulimit -n (number of open file)
2. set new limitation temporarily
ulimit -n newvalue
3. set new limitation permenant
3.1 vi /etc/security/limits.conf
add
username - nofile 2048
3.2. sysctl -p
4. set limitation system-wide
4.1 vi /etc/sysctl.conf
4.2 sysctl -p
reference:
http://cherry.world.edoors.com/CPZKoGkpxfbQ
http://www.linuxquestions.org/questions/slackware-14/increasing-file-descriptors-228004/
http://www.xenoclast.org/doc/benchmark/HTTP-benchmarking-HOWTO/node7.html
Process for service Admin Console failed to start - informatica 9.1.0 hf3 installation.
1. got following error when install informatica 9.1.0 HF3
OutPut : [ICMD_10033] Command [ping] failed with error [[INFACMD_10053] Service [_AdminConsole] Domain [Domain_pncuatinformatica.evolvsuite.local] has failed to ping back.].
Error :
Troubleshooting Tips
1. Refer to the following log files for more information:
Administrator logs $INFA_HOME/tomcat/temp/_AdminConsole/logs : Refer to this file to debug issues related to the Administrator tool.
administrator.log $INFA_HOME/services/AdminConsole : This file contains some, but not all, log events pertaining to the Administrator tool.
2.Run the following command to enable the Informatica Administrator manually:
$INFA_HOME/isp/bin/infacmd.bat/sh enableservice -dn <MyDomain> -un Administrator -pd Administrator -sn _AdminConsole
Installation Status:WARNING
The Informatica 9.1.0 HotFix 3 installation is complete.
2. check $INFA_HOME/tomcat/logs/node.log
ERROR [Thread 6 of 6 in DomainServiceThreadPool] [SPC_10013] Process for service _AdminConsole failed to start.
3. check $INFA_HOME/tomcat/temp/_AdminConsole/logs
java.io.FileNotFoundException: /u01/app/informatica/tomcat/temp/_AdminConsole/work/_AdminConsole/localhost/administrator/tldCache.ser (Too many open files)
4. the problem is the open file limitation for user informatica was set to default 1024 in redhat linux.
5. unlimit -n 2048 as root
6. restart informatica. it is good.
OutPut : [ICMD_10033] Command [ping] failed with error [[INFACMD_10053] Service [_AdminConsole] Domain [Domain_pncuatinformatica.evolvsuite.local] has failed to ping back.].
Error :
Troubleshooting Tips
1. Refer to the following log files for more information:
Administrator logs $INFA_HOME/tomcat/temp/_AdminConsole/logs : Refer to this file to debug issues related to the Administrator tool.
administrator.log $INFA_HOME/services/AdminConsole : This file contains some, but not all, log events pertaining to the Administrator tool.
2.Run the following command to enable the Informatica Administrator manually:
$INFA_HOME/isp/bin/infacmd.bat/sh enableservice -dn <MyDomain> -un Administrator -pd Administrator -sn _AdminConsole
Installation Status:WARNING
The Informatica 9.1.0 HotFix 3 installation is complete.
2. check $INFA_HOME/tomcat/logs/node.log
ERROR [Thread 6 of 6 in DomainServiceThreadPool] [SPC_10013] Process for service _AdminConsole failed to start.
3. check $INFA_HOME/tomcat/temp/_AdminConsole/logs
java.io.FileNotFoundException: /u01/app/informatica/tomcat/temp/_AdminConsole/work/_AdminConsole/localhost/administrator/tldCache.ser (Too many open files)
4. the problem is the open file limitation for user informatica was set to default 1024 in redhat linux.
5. unlimit -n 2048 as root
6. restart informatica. it is good.
rman command
1. create spfile backup and control file backup
backup spfile format '/tmp/spfileorcl.ora';
backup current controlfile format '/tmp/controlorcl.copy';
2. restore spfile and control file
rman target /
starup force nomount
restore spfile from '/tmp/spfilecolouat2012_01_12.ora';
shutdown
startup nomount
restore controlfile from '/tmp/controlcolouat2012_01_12.ctl';
alter database mount
3.
RUN {
ALLOCATE CHANNEL ch1 TYPE
DISK FORMAT '/u01/backup/DB10G/%d_DB_%u_%s_%p';
BACKUP DATABASE PLUS ARCHIVELOG;
RELEASE CHANNEL ch1;
}
EXIT;
4. run scripts
#!/bin/bash
rman target / < LIST ARCHIVELOG ALL;
RMAN> LIST BACKUP OF ARCHIVELOG ALL;
RMAN> LIST BACKUP;
RMAN> LIST BACKUP OF DATABASE;
RMAN> LIST BACKUP OF DATAFILE 1;
RMAN> LIST BACKUP SUMMARY;
RMAN> LIST INCARNATION;
RMAN> LIST BACKUP BY FILE;
RMAN> LIST COPY OF DATABASE ARCHIVELOG ALL;
RMAN> LIST COPY OF DATAFILE 1, 2, 3;
RMAN> LIST BACKUP OF DATAFILE 11 SUMMARY;
RMAN> LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 1437;
RMAN> LIST CONTROLFILECOPY "/tmp/cntrlfile.copy";
RMAN> LIST BACKUPSET OF DATAFILE 1;
RMAN> LIST FAILURE;
RMAN> LIST FAILURE 641231 detail;
reference:
http://www.oracle-base.com/articles/misc/OracleShellScripting.php
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfa.htm
http://ss64.com/ora/rman_list.html
backup spfile format '/tmp/spfileorcl.ora';
backup current controlfile format '/tmp/controlorcl.copy';
2. restore spfile and control file
rman target /
starup force nomount
restore spfile from '/tmp/spfilecolouat2012_01_12.ora';
shutdown
startup nomount
restore controlfile from '/tmp/controlcolouat2012_01_12.ctl';
alter database mount
3.
RUN {
ALLOCATE CHANNEL ch1 TYPE
DISK FORMAT '/u01/backup/DB10G/%d_DB_%u_%s_%p';
BACKUP DATABASE PLUS ARCHIVELOG;
RELEASE CHANNEL ch1;
}
EXIT;
4. run scripts
#!/bin/bash
rman target / <
RMAN> LIST BACKUP OF ARCHIVELOG ALL;
RMAN> LIST BACKUP;
RMAN> LIST BACKUP OF DATABASE;
RMAN> LIST BACKUP OF DATAFILE 1;
RMAN> LIST BACKUP SUMMARY;
RMAN> LIST INCARNATION;
RMAN> LIST BACKUP BY FILE;
RMAN> LIST COPY OF DATABASE ARCHIVELOG ALL;
RMAN> LIST COPY OF DATAFILE 1, 2, 3;
RMAN> LIST BACKUP OF DATAFILE 11 SUMMARY;
RMAN> LIST BACKUP OF ARCHIVELOG FROM SEQUENCE 1437;
RMAN> LIST CONTROLFILECOPY "/tmp/cntrlfile.copy";
RMAN> LIST BACKUPSET OF DATAFILE 1;
RMAN> LIST FAILURE;
RMAN> LIST FAILURE 641231 detail;
Subscribe to:
Posts (Atom)