-01157 cannot identify/lock datafile string - see DBWR trace file

HI,
-01157 cannot identify/lock datafile string - see DBWR trace file
ora -1110 errors are throwing when iam going to startup

872565 wrote:
HI,
-01157 cannot identify/lock datafile string - see DBWR trace file
ora -1110 errors are throwing when iam going to startupDid you lookup this error on the Internet ??
What does the alert_log tell you??
The Google answer on this is:
ORA-01157:cannot identify/lock data file string - see DBWR trace file
Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified.
Action: Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES.
Edit: It is recommended to post database version and OS version also, including more information.
This post of you looks like:
Hi
My Car is not starting. It is smoking from behind and making the weirdest sounds
Please adviceCheers
FJFranken
Edited by: fjfranken on 19-jul-2011 5:33

Similar Messages

ORA-01157: cannot identify/lock data file 13 - see DBWR trace file

Hi all,
I've a Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
I'm using ASM.
Yesterday I added new disks and then I changed the +/etc/udev/rules.d/98-oracle.rules+ file.
Now it looks like this (the bolded are the new ones):
# Oracle Configuration Registry
KERNEL=="emcpowerd1", OWNER="root", GROUP="oinstall", MODE="640", NAME="ocr"
# Voting Disks
KERNEL=="emcpowerr1", OWNER="oracle", GROUP="oinstall", MODE="640", NAME="voting"
# Spfile ASM+
KERNEL=="emcpowers1", OWNER="oracle", GROUP="dba", MODE="660", NAME="spfileASM"
# ASM Devices
KERNEL=="emcpowerj1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm0" #onlineredo asm disk
KERNEL=="emcpowern1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm1" #data asm disk
KERNEL=="emcpowerh1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm2" #data asm disk
KERNEL=="emcpowerq1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm3" #data asm disk
KERNEL=="emcpowere1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm4" #data asm disk
KERNEL=="emcpowerg1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm5" #data asm disk
KERNEL=="emcpowerl1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm6" #data asm disk
KERNEL=="emcpowero1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm7" #data asm disk
KERNEL=="emcpowerf1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm8" #data asm disk
KERNEL=="emcpowerm1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm9" #data asm disk
KERNEL=="emcpoweri1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm10" #data asm disk
KERNEL=="emcpowerp1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm11" #data asm disk
KERNEL=="emcpowerk1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm12" #data asm disk
KERNEL=="emcpowert", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm210" #data asm disk SATA
KERNEL=="emcpowerc", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm211" #data asm disk SATA
KERNEL=="emcpowerb", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm212" #data asm disk SATA
KERNEL=="emcpowera", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm213" #data asm disk SATA
It's the same on both RAC nodes.
The operating system, a RedHat 5.4, see the new devices (both nodes):
ls -ltr /dev/asm*
brw-rw---- 1 oracle dba 120, 16 May 18 10:03 /dev/asm212
brw-rw---- 1 oracle dba 120, 304 May 18 10:03 /dev/asm210
brw-rw---- 1 oracle dba 120, 32 May 18 10:03 /dev/asm211
brw-rw---- 1 oracle dba 120, 0 May 18 10:03 /dev/asm213
brw-rw---- 1 oracle dba 120, 209 May 18 10:05 /dev/asm1
brw-rw---- 1 oracle dba 120, 81 May 18 13:40 /dev/asm8
brw-rw---- 1 oracle dba 120, 97 May 18 13:40 /dev/asm5
brw-rw---- 1 oracle dba 120, 193 May 18 13:40 /dev/asm9
brw-rw---- 1 oracle dba 120, 161 May 18 13:40 /dev/asm12
brw-rw---- 1 oracle dba 120, 241 May 18 13:40 /dev/asm11
brw-rw---- 1 oracle dba 120, 177 May 18 13:40 /dev/asm6
brw-rw---- 1 oracle dba 120, 225 May 18 13:40 /dev/asm7
brw-rw---- 1 oracle dba 120, 65 May 18 13:40 /dev/asm4
brw-rw---- 1 oracle dba 120, 129 May 18 13:40 /dev/asm10
brw-rw---- 1 oracle dba 120, 257 May 18 13:40 /dev/asm3
brw-rw---- 1 oracle dba 120, 113 May 18 13:40 /dev/asm2
brw-rw---- 1 oracle dba 120, 145 May 18 13:40 /dev/asm0
Both ASM instance see new devices:
From ASM1
SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:43:10 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM1
SQL> select path from v$asm_disk;
PATH
/dev/asm212
/dev/asm211
/dev/asm213
/dev/asm210
/dev/asm1
/dev/asm4
/dev/asm5
/dev/asm0
/dev/asm12
/dev/asm9
/dev/asm2
/dev/asm10
/dev/asm7
/dev/asm11
/dev/asm3
/dev/asm8
/dev/asm6
17 rows selected.
SQL>
From ASM2
SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:42:39 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM2
SQL> select path from v$asm_disk;
PATH
/dev/asm213
/dev/asm211
/dev/asm210
/dev/asm212
/dev/asm8
/dev/asm7
/dev/asm6
/dev/asm11
/dev/asm4
/dev/asm12
/dev/asm5
/dev/asm9
/dev/asm1
/dev/asm3
/dev/asm10
/dev/asm2
/dev/asm0
17 rows selected.
SQL>
Then I created a disk group:
CREATE DISKGROUP STORE EXTERNAL REDUNDANCY DISK '/dev/asm210';
Then I created a new tablespace:
CREATE TABLESPACE store DATAFILE '+STORE';
I did all this operations from NODE1.
What is happening now is that everytime I try to read something from new diskgroup FROM NODE2 I get the ORA-01157:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707
No problem to read from NODE1.
The simple query on dba_data_file work from NODE1 and fails from NODE2 with the ORA-01157.
I found this on the alert log:
<msg time='2010-05-18T10:06:41.084+00:00' org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
module='' pid='11014'>
<txt>Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
</txt>
</msg>
And this from the trace:
Trace file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
System name: Linux
Node name: node02
Release: 2.6.18-128.7.1.el5
Version: #1 SMP Wed Aug 19 04:00:49 EDT 2009
Machine: x86_64
Instance name: EVODB2
Redo thread mounted by this instance: 2
Oracle process number: 19
Unix process pid: 11014, image: oracle@node02 (SMON)
*** 2010-05-18 10:06:41.084
*** SESSION ID:(151.1) 2010-05-18 10:06:41.084
*** CLIENT ID:() 2010-05-18 10:06:41.084
*** SERVICE NAME:(SYS$BACKGROUND) 2010-05-18 10:06:41.084
*** MODULE NAME:() 2010-05-18 10:06:41.084
*** ACTION NAME:() 2010-05-18 10:06:41.084
DDE rules only execution for: ORA 1110
----- START Event Driven Actions Dump ----
---- END Event Driven Actions Dump ----
----- START DDE Actions Dump -----
----- DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
Successfully dispatched
----- (Action duration in csec: 0) -----
----- END DDE Actions Dump -----
*** 2010-05-18 10:06:41.084
SMON: following errors trapped and ignored:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
Any suggestion about how to solve the problem?
Thanks in advance!
Samuel

I didn't understand what do you mean with thread...
But I think you found the problem
Initialization files of both ASM instance are: SPFILE='/dev/spfileASM'
that SPFILE is (common for both):
+ASM2.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
+ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
+ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'#Manual Mount
*.asm_diskstring='/dev/asm*'
*.cluster_database=true
*.diagnostic_dest='/u01/app/oracle'
+ASM1.instance_number=1
+ASM2.instance_number=2
*.instance_type='asm'
*.large_pool_size=12M
+ASM1.local_listener='LISTENER_ASM'
+AC
Then I executed another query:
From ASM1
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM1
SQL> select name, state from v$asm_diskgroup;
NAME STATE
ARCHIVELOG MOUNTED
DATA MOUNTED
ONLINELOG MOUNTED
STORE MOUNTED
SQL>
From ASM2
SQL> select instance_name from v$instance;
INSTANCE_NAME
+ASM2
SQL> select name, state from v$asm_diskgroup;
NAME STATE
ARCHIVELOG MOUNTED
DATA MOUNTED
ONLINELOG MOUNTED
STORE DISMOUNTED
SQL>
Than the question is:
how can I mount the disk group STORE also on ASM2?
I think the problems is into the spfile lines:
+ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
+ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'
How can I change the +ASM2.asm_diskgroups value?
Thanks

Java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DB

I am deploying my application components on Oracle RAC database, when i install my app component i will run a script which creates a user and tablespace on bot rac-nodes(node1 and node2)
as database is clustered, the user are created on 2 nodes and tablespace is stored in a shared location for two rac nodes
i am able to successfully run my script on rac-node1 and and installed my component and when i started installing the app component on node2 getting error
java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: '/db/db/db/ora10g/10.2.0/admin/dbadmin_01.dbf'
ORA-06512: at "ADMIN.XL_SP_DBCHECK", line 48
ORA-06512: at line 1
"dbadmin_01.dbf is the custom tablespace which created by me"
i a mgetting error while installing the app component on rac-node2

You should not create database files outside of the ASM.
I'm not sure you can move the datafile, I would export the data from the tablespace (if there is data you need there), delete the tablespace and recreate it in the ASM, then import the data back.
If you want to move the datafile, you can try using RMAN (from node1).
First connect to the database with sqlplus and execute:
alter tablespace <tbs_name> offline;Then start RMAN: rman target /
BACKUP AS COPY DATAFILE '<file>' FORMAT '+<ASM_DG>';Then in sqlplus, execute:
alter tablespace <tbs_name> online;I'm not sure it will work, and I hope I got the commands right because I can't check it right now.
Good luck
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Java.sql.SQLException: ORA-01157: cannot identify/lock data file : PLz Help

My datafiles are in ASM file system, however the only one file ACIPEN_DATA is the one, which is not in ASM file system, and this the file which is in concern.
We are getting the following exception in the lxkratgas1.lex1.lexmark.com when connecting to ACIPEN_DATA.
This exception is coming up sometimes and the sometimes the file is getting processed successfully
Caused by: java.sql.SQLException: ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: '/oracle/SE/product/10.2.0/db_1/dbs/ACIPEN_DATA'
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1169)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:278)
at atg.adapter.gsa.SQLStatement.executeUpdate(SQLStatement.java:725)
at atg.adapter.gsa.Table.insert(Table.java:1378)
at atg.adapter.gsa.GSAItemDescriptor.addItem(GSAItemDescriptor.java:6272)
... 61 more
====================================================================
We have checked the datafile, it is absolutely online.
Can some expert jump in and resolve this issue Please.

01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause: The background process was either unable to find one of the data
//         files or failed to lock it because the file was already in use.
//         The database will prohibit access to this file but other files will
//         be unaffected. However the first instance to open the database will
//         need to access all online data files. Accompanying error from the
//         operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
//         open the database or do ALTER SYSTEM CHECK DATAFILES.is this a RAC database?

ASM diskgroups unmounting, getting ORA-01157: cannot identify/lock data fil

All,
We've recently purchased a RAMSAN device for better throughput. I created the initial diskgroup with the following syntax:
CREATE DISKGROUP EMTPRD0X_SSD01 NORMAL REDUNDANCY
FAILGROUP RS1 DISK '/dev/rdsk_ramsan_primary' NAME ssd_prim
FAILGROUP RS2 DISK '/dev/rdsk_ramsan_backup' NAME ssd_bkup;
and then created a temporary tablespace on top of that diskgroup:
create temporary tablespace temp04 tempfile '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g;
Everything seemed fine at first and then end users started seeing the following errors in the alert log:
SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
Tue Oct 12 16:12:51 2010
Errors in file /opt/oracle/oradump/emtprd02/udump/emtprd02_ora_11578.trc:
ORA-01157: cannot identify/lock data file 3009 - see DBWR trace file
ORA-01110: data file 3009: '+EMTPRD0X_SSD01/emtprd0x/tempfile/temp04.256.732210281'
After talking with Oracle support I was told that the only workaround for diskgroups unmounting themselves is to put a control file/redo log/dummy tablespace inside of that diskgroup and continually write/read from it.
Does that make sense?
They pointed me to note 603204.1 - Why FRA Diskgroup Gets Mounted/Dismounted.
The system is a 3 node Oracle 10.2.0.4 rac running on ASM Solaris x86 64bit.
Any ideas?
Thanks,
Brian

Post Operating System (OS) name & version for DB server system.
Post results of
SELECT * from v$version
My db is not in archivelog mode poor choice
and no backup was taken. Worse choise
Is there any way I can recover this db? Recover as in no data loss?
Very doubtful.
Possible to open with data loss.
01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause: The background process was either unable to find one of the data
//         files or failed to lock it because the file was already in use.
//         The database will prohibit access to this file but other files will
//         be unaffected. However the first instance to open the database will
//         need to access all online data files. Accompanying error from the
//         operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
//         open the database or do ALTER SYSTEM CHECK DATAFILES.What exactly cause this mess?
Edited by: sb92075 on Jan 7, 2010 8:59 PM

ORA-01157: cannot identify/lock data file error in standby database.

Hi,
i have a primary database and standby database (11.2.0.1.0) running in ASM with different diskgroup names. I applied an incremental backup on standby database to resolve archive log gap and generated a controlfile for standby in primary database and restored the controlfile in standby database.But when i started the MRP process its not starting and thows error in alert log ORA-01157: cannot identify/lock data file. When i queried the standby database file it shows the location on primary database datafiles names not the standby database.
PRIMARY DATABASE
SQL> select name from v$datafile;
NAME
+DATA/oradb/datafile/system.256.788911005
+DATA/oradb/datafile/sysaux.257.788911005
+DATA/oradb/datafile/undotbs1.258.788911005
+DATA/oradb/datafile/users.259.788911005
STANDBY DATABASE
SQL> select name from v$datafile;
NAME
+STDBY/oradb/datafile/system.256.788911005
+STDBY/oradb/datafile/sysaux.257.788911005
+STDBY/oradb/datafile/undotbs1.258.788911005
+STDBY/oradb/datafile/users.259.788911005
The Actual physical location of standby database files in ASM in standby server is shown below
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
ASMCMD>
ASMCMD> ls
SYSAUX.259.805921967
SYSTEM.258.805921881
UNDOTBS1.260.805922023
USERS.261.805922029
ASMCMD>
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
i even tried to rename the datafiles in standby database but it throws error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Regards,
007

Hi saurabh,
I tried to rename the datafiles in standby database after restoring it throws the below error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Also in my pfile i have mentioned the below parameters
*.db_create_file_dest='+STDBY'
*.db_domain=''
*.db_file_name_convert='+DATA','+STDBY'
*.db_name='ORADB'
*.db_unique_name='11GDB'
Regards,
007

MDDataSetBW.GetCellData. See RFC trace file or SAP system log for more...

Ingo,
I am getting below error message in BO Test environment when I refresh WebI document.
MDDataSetBW.GetCellData. See RFC trace file or SAP system log for more details
It was working when we migrated the objects initially. Subsequently when we try to refresh WebI document we are getting the above error message. It still works in BO Dev environment and the no of records are the same in Dev and Test.
I am able run the underlying BEx query in SAP BW Test environment and it does return data.
I checked ST22 and SM21 log, but no details there.
Is it related to Authorization on the Universe or Bex Query?
We are in the middle of UAT and not able to move forward. I would greatly appreciate your input.
Thanks
Ram

Ingo,
I ran the zip file and added the required entries to registry.
And then I tried to reproduce the error, but the files are not generated instead I noticeed below error message on the server:
The description for Event ID ( 7939 ) in Source ( Crystal OLAP Client ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Registry Access Error: , [HKEY_LOCAL_MACHINE]Software\Business Objects\Suite 12.0\MDA\Log\Modules: The system cannot find the file specified..
Does tha t mean we do not have permissons to read the registry?
I would greatly appreciate your input.
Thanks in advance.
Ram

Unable to start the database(Process m000 died, see its trace file)

Hi,
Oracle Version:10.2.0.1
Operating System:Linux
Hi suddenly the database went down and in alert logfile it is showing error like this.
Fri Feb 18 01:40:51 2011
Process m000 died, see its trace file
Fri Feb 18 01:40:51 2011
ksvcreate: Process(m000) creation failed
Fri Feb 18 01:41:18 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_15998.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
Fri Feb 18 01:41:19 2011
Process m000 died, see its trace file
Fri Feb 18 01:41:19 2011
ksvcreate: Process(m000) creation failed
Fri Feb 18 01:42:19 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_16032.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
Fri Feb 18 01:42:20 2011
Process m000 died, see its trace file
Fri Feb 18 01:42:20 2011
ksvcreate: Process(m000) creation failed
Fri Feb 18 01:43:20 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_16036.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
Fri Feb 18 01:43:21 2011
Process m000 died, see its trace file
Fri Feb 18 01:43:21 2011
ksvcreate: Process(m000) creation failed
Fri Feb 18 01:44:21 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_16042.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
Fri Feb 18 01:44:22 2011
Process m000 died, see its trace file
Fri Feb 18 01:44:22 2011
ksvcreate: Process(m000) creation failedand generating lot of trace files.
Please help me how to solve this .
Thanks & Regards,
Poorna Prasad.

In my alert log file I also find this error.
ed Feb 16 06:11:13 2011
Process J000 died, see its trace file
Wed Feb 16 06:11:13 2011
kkjcre1p: unable to spawn jobq slave process
Wed Feb 16 06:11:13 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_cjq0_26196.trc:
Wed Feb 16 06:11:13 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_j000_4172.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
Wed Feb 16 06:11:14 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_j000_4172.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
Process J000 died, see its trace file
Wed Feb 16 06:11:14 2011
kkjcre1p: unable to spawn jobq slave process
Wed Feb 16 06:11:14 2011
Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_cjq0_26196.trc:Thanks & Regards,
Poorna Prasad.S

Process m000 died, see its trace file

Oracle keeps crashing. When i look at the log, i'm seeing Process m000 died, see its trace file. In the trace file, i see the following error message.
Process m000 is dead (pid=20243, state=3):
Unable to schedule a MMON slave at: Auto Flush Main 1
Attempt to create slave process failed.
Can happen for several reasons:
- No process state objects
- Reached OS set limits
- A shutdown was going on
Check alert log for more details.
Does anyone know what is causing this? We are currently running Oracle 10.2.0.4 on solaris 10.

Metalink note : 458981.1
Unable to Schedule a MMON Slave Message in Trace File After Enable/Disable Restricted Session
Bug 3599698 - ENABLE RESTRICTED SESSION/IMPORT/DISABLE RESTRICTED SESSION GENERATES TRACE
-Anantha

Process m001 died, see its trace file

Hi
Kindly tell why process died & look at the trace file
Process m001 died, see its trace file
Thu Dec 28 14:30:53 2006
ksvcreate: Process(m001) creation failed
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Windows 2000 Version V5.0 Service Pack 3
CPU : 4 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:443M/2047M, Ph+PgF:3071M/4967M, VA:1572M/2047M
Instance name: xxxx
Redo thread mounted by this instance: 1
Oracle process number: 11
Windows thread id: 4712, image: ORACLE.EXE (MMON)
*** SERVICE NAME:(SYS$BACKGROUND) 2006-12-26 18:31:12.750
*** SESSION ID:(29.1) 2006-12-26 18:31:12.750
*** 2006-12-26 18:31:12.750
Process m001 is dead (pid=5516, state=3):
*** 2006-12-27 15:30:13.421
Process m001 is dead (pid=6128, state=3):
*** 2006-12-27 16:31:07.359
Process m001 is dead (pid=5572, state=3):
*** 2006-12-28 14:30:53.312
Process m001 is dead (pid=5792, state=3):

According to
KSVCREATE: PROCESS(M000) CREATION FAILED' MESSAGES IN ALERT LOG
Doc ID: Note:352388.1 Type: PROBLEM
Last Revision Date: 14-SEP-2006 Status: PUBLISHED
you should increase the PROCESSES parameter of your database instance.

Process J000 died, see its trace file

os：centos5.4 64
db：oracle 11.2.0.3
alert日志中经常出现以下告警（有时候1分钟报好几次）：
Process m000 died, see its trace file
Process J000 died, see its trace file :
kkjcre1p: unable to spawn jobq slave process
Errors in file 。。。。
SQL> show parameter job
NAME TYPE VALUE
job_queue_processes integer 1000
SQL> show parameter parallel_max_servers
NAME TYPE VALUE
parallel_max_servers integer 320

谢谢您的回复。
数据库异常时间是 11月1号早上9点10分左右。
alert发您邮箱了[email protected]。
trace里面没看到内容。
tmpfs 21G 13G 8.1G 62% /dev/shm
物理内存 24G
swap 4G
memory_max_target 20G
memory_target 20G
sga_max_size 20G
不知道我这样的内存分配，会不会合理呢？
帖子经 961972编辑过

After adding datafile with OEM a trace file genarating in alertSID.log file

Hi to All,
I have added a datafile with OEM but while adding its taking some time so terminated that program and added the datafile with command prompt but after some time i seen that datafile in datafile list and after this thing Im getting error and our server is very slow users gettting access to over server very slow and a trace file is generating in over alertSID.log file.with system language.

user12239004 wrote:
Hi anurag,
# ls -lart /dev/vx/rdsk/datadg |grep his_link_y10_01_index
crw------- 1 oracle dba 315,129093 Mar 14 09:53 his_link_y10_01_index_ts01
crw------- 1 root root 315,129077 Mar 15 13:58 his_link_y10_01_index_ts02
# chown oracle:dba his_link_y10_01_index_ts02
# ls -lart /dev/vx/rdsk/datadg |grep his_link_y10_01_index
crw------- 1 oracle dba 315,129093 Mar 14 09:53 his_link_y10_01_index_ts01
crw------- 1 oracle dba 315,129077 Mar 15 13:58 his_link_y10_01_index_ts02
root : root , I have changed the permisison now .. hope the error will subside and my next startup will be smooth
Regards,Great,
So give a try and let us know if you see any problem.
Regards
Anurag

I am not able to see the trace files for SQL query

Hello, I am using windows vista OS.
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for 32-bit Windows: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production
SQL>
I enabled the trace as below
alter system set timed_statistics=TRUE
alter system set sql_trace=TRUE
After this, I ran sql query from scott as below.
select count(*) from emp;
After this, i checked in user dump directory. The trace files are generating... But this sql code is not appearing in the trace files...
Am i missing anything... Any help is appreciated.
Thanks

This may happen when the trace file is not completely closed.You may try again doing like this,
alter session set sql_trace=true;
select * from emp;
alter session set sql_trace=false;After this,disconnect and exit from your session as well. This should close the file completely and you should be able to see your command in it.
HTH
Aman....

Cannot identify lock screen icon on Lumia 520

There is an icon at bottom of my lock screen that I can't find an explanation for. It appears to be a square with a circle inside, with the typical email envelope icon coming out to its right, and the number 2 to right of both of those. I have no unread emails or text messages so can't for the life of my figure out what the "2" is supposed to indicate. No explanation in user manual. See photo.
Attachments:
wp_ss_20150221_0001.jpg ‏89 KB

It is your email notification.

SM12 Identifying locked vehicle

I have an issue where 4 vehicles are showing the message that they are locked when the users attempt an action. We believe the lock message to be bad / data and that they just need to be unlocked by support to continue.
I am looking in SM12, however, and while I can see locked lines as they come up /refresh, I cannot identify which are related to these four vehicles? There appears to be no identifying information - I have tried searching the document numbers and vehicle IDs for the vehicles (with wildcards on either side) in the lock argument field, and i've tried reviewing the available data in the results from just an open search of current locks for all users/vehicles, but no luck.
Is there another screen or place on the vehicles I can look to connect the data visible for a lock in SM12 with the machines in question and verify that I have the right locks before I unlock them?

I don't think vehicle ID will be shown in SM12. You need to identify the table that holds the vehicle ID, then use the table in the table name field to find the locks.
Regards,

-01157 cannot identify/lock datafile string - see DBWR trace file

Similar Messages

Maybe you are looking for