ADRCI (Automatic Diagnostic Repository (ADR) Command Interpreter) in oracle database 11g

This is not complete document , i wrote here just for a example. i will write details and nicely after some days later.

ADRCI
==============
(ADR Command Interpreter) in oracle database 11g

Automatic Diagnostic Repository (ADR) Command Interpreter in oracle database 11g

SEE HERE DETAILS :

http://download.oracle.com/docs/cd/B28359_01/server.111/b28319/adrci.htm#BABBHGFC

ADRCI is a command-line tool that is part of the fault diagnosability infrastructure introduced in Oracle Database Release 11g. ADRCI enables you to:

1) View diagnostic data within the Automatic Diagnostic Repository (ADR).

2) View Health Monitor reports.

3) Package incident and problem information into a zip file for transmission to Oracle Support.

Diagnostic data includes incident and problem descriptions, trace files, dumps, health monitor reports, alert log entries, and more.

ADRCI has a rich command set, and can be used in interactive mode or within scripts. In addition, ADRCI can execute scripts of ADRCI commands in the same way that SQL*Plus executes scripts of SQL and PL/SQL commands.

ADR data is secured by operating system permissions on the ADR directories, hence there is no need to log in to ADRCI.





Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>ADRCI

ADRCI: Release 11.1.0.6.0 - Beta on Tue Jun 14 12:07:44 2011

Copyright (c) 1982, 2007, Oracle. All rights reserved.

ADR base = "g:\app\administrator"
adrci>
adrci> SPOOL C:/ADRCI.TXT
adrci>
adrci> SHOW HOME
ADR Homes:
diag\clients\user_administrator\host_1446532089_11
diag\clients\user_system\host_1446532089_11
diag\clients\user_unknown\host_411310321_11
diag\rdbms\halimdb\halimdb
diag\tnslsnr\xpsp3-wbb\listener
adrci>
adrci> SHOW HOMEPATH
ADR Homes:
diag\clients\user_administrator\host_1446532089_11
diag\clients\user_system\host_1446532089_11
diag\clients\user_unknown\host_411310321_11
diag\rdbms\halimdb\halimdb
diag\tnslsnr\xpsp3-wbb\listener
adrci>
adrci>
adrci> HELP

HELP [topic]
Available Topics:
CREATE REPORT
ECHO
EXIT
HELP
HOST
IPS
PURGE
RUN
SET BASE
SET BROWSER
SET CONTROL
SET ECHO
SET EDITOR
SET HOMES | HOME | HOMEPATH
SET TERMOUT
SHOW ALERT
SHOW BASE
SHOW CONTROL
SHOW HM_RUN
SHOW HOMES | HOME | HOMEPATH
SHOW INCDIR
SHOW INCIDENT
SHOW PROBLEM
SHOW REPORT
SHOW TRACEFILE
SPOOL

There are other commands intended to be used directly by Oracle, type
"HELP EXTENDED" to see the list

adrci> HELP EXTENDED

HELP [topic]
Available Topics:
BEGIN BACKUP
CD
DDE
DEFINE
DESCRIBE
END BACKUP
LIST DEFINE
MERGE ALERT
MERGE FILE
QUERY
SET COLUMN
SHOW CATALOG
SHOW DUMP
SHOW SECTION
SHOW TRACE
SHOW TRACEMAP
SWEEP
UNDEFINE
VIEW
adrci>
adrci>
adrci> HELP SHOW ALETR
DIA-48433: Unknown help topic

adrci> HELP SHOW TRACEFILE

Usage: SHOW TRACEFILE [file1 file2 ...] [-rt | -t]
[-i inc1 inc2 ...] [-path path1 path2 ...]

Purpose: List the qualified trace filenames.
Options:
[file1 file2 ...]: The trace files users are interested in to search.
If "-i" or/and "-path" is specified, the trace files are assumed
to be under the specified incidents or paths. Otherwise, the files
will be searched among the trace directory and all incident directories
of the current ADR homes. Filenames allow SQL like condition syntax.
I.e., allowing wildcard search on filenames by using "%". For example,
"%mmon%" means all trace files with the "mmon" substring.

[-rt | -t]: Order the trace filenames. "-t" means in the modified
timestamps order; "-rt" means in the reversed modified timestamps
order. Note that the ordering is only apply to a single directory.
[-i inc1 inc2 ...]: The trace files produced for the listed incidents.
If no files are listed, all trace files produced for the list
incidents are considered.

[-path path1 path2 ...]: The trace files under the given paths will be
queried. If no files are listed, all trace files under these paths
are considered.

Examples:
1. Show all the trace files under the current home
"show tracefile"
2. Show all the mmon trace files in time reverse order
"show tracefile %mmon% -rt"
3. Show all trace files under incidents 123 456, and /home/someone/temp
"show tracefile -i 123 456 -path /home/someone/temp"

adrci>
adrci>
adrci> ADRCI -HELP
DIA-48415: Syntax error found in string [ADRCI -HELP] at column [11]

adrci> ADRCI HELP
DIA-48415: Syntax error found in string [ADRCI HELP] at column [10]

adrci>
adrci>
adrci> SHOW ALETR -TAIL
DIA-48415: Syntax error found in string [SHOW ALETR] at column [10]

adrci> SHOW ALERT -TAIL
DIA-48449: Tail alert can only apply to single ADR home

adrci>
adrci>
adrci> SET HOME diag\rdbms\halimdb\halimdb
adrci>
adrci> SHOW ALERT -TAIL
2011-06-14 12:00:22.109000 +06:00
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
2011-06-14 12:00:23.562000 +06:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=21, OS id=1244
SMCO started with pid=22, OS id=3472
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-06-14 12:00:25.609000 +06:00
Starting background process QMNC
QMNC started with pid=23, OS id=4052
2011-06-14 12:00:36.796000 +06:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-06-14 12:00:48.359000 +06:00
Completed: alter database open
2011-06-14 12:05:07.578000 +06:00
Starting background process CJQ0
CJQ0 started with pid=7, OS id=1748
2011-06-14 12:05:18.171000 +06:00
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_j00
9_2164.trc:
ORA-12012: error on auto execute of job 11689
ORA-01403: no data found
adrci>
adrci>
adrci>
adrci> SHOW ALERT -TAIL 10
2011-06-14 12:00:22.109000 +06:00
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
2011-06-14 12:00:23.562000 +06:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=21, OS id=1244
SMCO started with pid=22, OS id=3472
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-06-14 12:00:25.609000 +06:00
Starting background process QMNC
QMNC started with pid=23, OS id=4052
2011-06-14 12:00:36.796000 +06:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-06-14 12:00:48.359000 +06:00
Completed: alter database open
2011-06-14 12:05:07.578000 +06:00
Starting background process CJQ0
CJQ0 started with pid=7, OS id=1748
2011-06-14 12:05:18.171000 +06:00
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_j00
9_2164.trc:
ORA-12012: error on auto execute of job 11689
ORA-01403: no data found
adrci>
adrci>
adrci> SHOW ALERT -TAIL -F
2011-06-14 12:00:22.109000 +06:00
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
2011-06-14 12:00:23.562000 +06:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=21, OS id=1244
SMCO started with pid=22, OS id=3472
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-06-14 12:00:25.609000 +06:00
Starting background process QMNC
QMNC started with pid=23, OS id=4052
2011-06-14 12:00:36.796000 +06:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-06-14 12:00:48.359000 +06:00
Completed: alter database open
2011-06-14 12:05:07.578000 +06:00
Starting background process CJQ0
CJQ0 started with pid=7, OS id=1748
2011-06-14 12:05:18.171000 +06:00
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_j00
9_2164.trc:
ORA-12012: error on auto execute of job 11689
ORA-01403: no data found
^C
C:\Documents and Settings\Administrator>Q
'Q' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>ADRCI

ADRCI: Release 11.1.0.6.0 - Beta on Tue Jun 14 12:13:05 2011

Copyright (c) 1982, 2007, Oracle. All rights reserved.

ADR base = "g:\app\administrator"
adrci>
adrci>
adrci> SHOW ALERT -P "MESSAGE_TEXT LIKE '%ORA-600%'"

Choose the alert log from the following homes to view:

1: diag\clients\user_administrator\host_1446532089_11
2: diag\clients\user_system\host_1446532089_11
3: diag\clients\user_unknown\host_411310321_11
4: diag\rdbms\halimdb\halimdb
5: diag\tnslsnr\xpsp3-wbb\listener
Q: to quit

Please select option:
The option is invalid.

Please select option: 4

Please select option: 4

Please select option: Q
adrci>
adrci>
adrci> SET HOME diag\rdbms\halimdb\halimdb
adrci> SHOW ALERT -P "MESSAGE_TEXT LIKE '%ORA-600%'"

ADR Home = g:\app\administrator\diag\rdbms\halimdb\halimdb:
*************************************************************************
adrci>
adrci>
adrci> SHOW ALERT -P "MESSAGE_TEXT LIKE '%ORA-600%'"

ADR Home = g:\app\administrator\diag\rdbms\halimdb\halimdb:
*************************************************************************
adrci>
adrci> SHOW ALERT -TERM

ADR Home = g:\app\administrator\diag\rdbms\halimdb\halimdb:
*************************************************************************
2011-05-10 07:01:47.120000 +02:00
Starting ORACLE instance (normal)
2011-05-10 07:01:48.995000 +02:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
2011-05-10 07:01:50.057000 +02:00
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
2011-05-10 07:01:52.479000 +02:00
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in client-side pfile G:\APP\ADMINISTRATOR\ADMIN\HALIMDB
\PFILE\INIT.ORA on machine XPSP3-WBB
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
2011-05-10 07:01:53.729000 +02:00
PMON started with pid=2, OS id=2664
VKTM started with pid=3, OS id=2936 at elevated priority
DIAG started with pid=4, OS id=2856
PSP0 started with pid=6, OS id=2956
DBRM started with pid=5, OS id=884
VKTM running at (20)ms precision
DIA0 started with pid=8, OS id=2860
DSKM started with pid=7, OS id=1796
MMAN started with pid=9, OS id=2372
2011-05-10 07:01:55.870000 +02:00
DBW0 started with pid=10, OS id=2228
LGWR started with pid=11, OS id=2408
CKPT started with pid=12, OS id=2260
SMON started with pid=13, OS id=3708
RECO started with pid=14, OS id=1164
MMON started with pid=15, OS id=2988
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
MMNL started with pid=16, OS id=1812
2011-05-10 07:01:58.932000 +02:00
starting up 1 shared server(s) ...
ORACLE_BASE from environment = G:\app\Administrator
2011-05-10 07:02:03.870000 +02:00
Full restore complete of datafile 4 to datafile copy G:\APP\ADMINISTRATOR\ORADAT
A\HALIMDB\USERS01.DBF. Elapsed time: 0:00:01
checkpoint is 886307
Full restore complete of datafile 3 to datafile copy G:\APP\ADMINISTRATOR\ORADAT
A\HALIMDB\UNDOTBS01.DBF. Elapsed time: 0:00:01
checkpoint is 886307
2011-05-10 07:02:59.901000 +02:00
Full restore complete of datafile 2 to datafile copy G:\APP\ADMINISTRATOR\ORADAT
A\HALIMDB\SYSAUX01.DBF. Elapsed time: 0:00:57
checkpoint is 886307
last deallocation scn is 885939
2011-05-10 07:03:07.573000 +02:00
Full restore complete of datafile 1 to datafile copy G:\APP\ADMINISTRATOR\ORADAT
A\HALIMDB\SYSTEM01.DBF. Elapsed time: 0:01:05
checkpoint is 886307
last deallocation scn is 881147
Undo Optimization current scn is 826974
Create controlfile reuse set database "halimdb"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'G:\app\Administrator\oradata\halimdb\SYSTEM01.DBF',
'G:\app\Administrator\oradata\halimdb\SYSAUX01.DBF',
'G:\app\Administrator\oradata\halimdb\UNDOTBS01.DBF',
'G:\app\Administrator\oradata\halimdb\USERS01.DBF'
LOGFILE GROUP 1 ('G:\app\Administrator\oradata\halimdb\redo01.log') SIZE 51200K,

GROUP 2 ('G:\app\Administrator\oradata\halimdb\redo02.log') SIZE 51200K,
GROUP 3 ('G:\app\Administrator\oradata\halimdb\redo03.log') SIZE 51200K RESETLOG
S
WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
Default Temporary Tablespace will be necessary for a locally managed database in
future release
2011-05-10 07:03:08.932000 +02:00
Setting recovery target incarnation to 1
Successful mount of redo thread 1, with mount id 3146928939
Completed: Create controlfile reuse set database "halimdb"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'G:\app\Administrator\oradata\halimdb\SYSTEM01.DBF',
'G:\app\Administrator\oradata\halimdb\SYSAUX01.DBF',
'G:\app\Administrator\oradata\halimdb\UNDOTBS01.DBF',
'G:\app\Administrator\oradata\halimdb\USERS01.DBF'
LOGFILE GROUP 1 ('G:\app\Administrator\oradata\halimdb\redo01.log') SIZE 51200K,

GROUP 2 ('G:\app\Administrator\oradata\halimdb\redo02.log') SIZE 51200K,
GROUP 3 ('G:\app\Administrator\oradata\halimdb\redo03.log') SIZE 51200K RESETLOG
S
Shutting down instance: further logons disabled
Stopping background process MMNL
2011-05-10 07:03:10.854000 +02:00
Stopping background process MMON
Shutting down instance (immediate)
License high water mark = 1
Waiting for dispatcher 'D000' to shutdown
2011-05-10 07:03:12.901000 +02:00
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
2011-05-10 07:03:14.401000 +02:00
ARCH: Archival disabled due to shutdown: 1089
Stopping background process VKTM:
Shutting down archive processes
2011-05-10 07:03:15.416000 +02:00
Archiving is disabled
Archive process shutdown avoided: 0 active
2011-05-10 07:03:17.573000 +02:00
Instance shutdown complete
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in client-side pfile G:\APP\ADMINISTRATOR\CFGTOOLLOGS\D
BCA\HALIMDB\INITHALIMDBTEMP.ORA on machine XPSP3-WBB
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
_no_recovery_through_resetlogs= TRUE
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
PMON started with pid=2, OS id=2220
VKTM started with pid=3, OS id=2624 at elevated priority
DIAG started with pid=4, OS id=624
PSP0 started with pid=6, OS id=2588
DSKM started with pid=7, OS id=2432
MMAN started with pid=9, OS id=2564
DIA0 started with pid=8, OS id=2448
DBW0 started with pid=7, OS id=3768
LGWR started with pid=10, OS id=3068
SMON started with pid=12, OS id=3876
RECO started with pid=13, OS id=3496
2011-05-10 07:03:18.604000 +02:00
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
starting up 1 shared server(s) ...
VKTM running at (20)ms precision
DBRM started with pid=5, OS id=4064
CKPT started with pid=11, OS id=2236
ORACLE_BASE from environment = G:\app\Administrator
MMON started with pid=14, OS id=2516
2011-05-10 07:03:19.682000 +02:00
Create controlfile reuse set database "halimdb"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'G:\app\Administrator\oradata\halimdb\SYSTEM01.DBF',
'G:\app\Administrator\oradata\halimdb\SYSAUX01.DBF',
'G:\app\Administrator\oradata\halimdb\UNDOTBS01.DBF',
'G:\app\Administrator\oradata\halimdb\USERS01.DBF'
LOGFILE GROUP 1 ('G:\app\Administrator\oradata\halimdb\redo01.log') SIZE 51200K,

GROUP 2 ('G:\app\Administrator\oradata\halimdb\redo02.log') SIZE 51200K,
GROUP 3 ('G:\app\Administrator\oradata\halimdb\redo03.log') SIZE 51200K RESETLOG
S
WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
Default Temporary Tablespace will be necessary for a locally managed database in
future release
MMNL started with pid=15, OS id=716
2011-05-10 07:03:22.635000 +02:00
Setting recovery target incarnation to 1
Successful mount of redo thread 1, with mount id 3146955065
Completed: Create controlfile reuse set database "halimdb"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'G:\app\Administrator\oradata\halimdb\SYSTEM01.DBF',
'G:\app\Administrator\oradata\halimdb\SYSAUX01.DBF',
'G:\app\Administrator\oradata\halimdb\UNDOTBS01.DBF',
'G:\app\Administrator\oradata\halimdb\USERS01.DBF'
LOGFILE GROUP 1 ('G:\app\Administrator\oradata\halimdb\redo01.log') SIZE 51200K,

GROUP 2 ('G:\app\Administrator\oradata\halimdb\redo02.log') SIZE 51200K,
GROUP 3 ('G:\app\Administrator\oradata\halimdb\redo03.log') SIZE 51200K RESETLOG
S
Stopping background process MMNL
2011-05-10 07:03:23.979000 +02:00
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
ALTER SYSTEM enable restricted session;
alter database "halimdb" open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 886307
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_ora
_2180.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO01.L
OG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
MMON started with pid=14, OS id=3328
MMNL started with pid=15, OS id=2600
2011-05-10 07:03:25.416000 +02:00
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_ora
_2180.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: 'G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.L
OG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_ora
_2180.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO03.L
OG'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
2011-05-10 07:03:27.698000 +02:00
Setting recovery target incarnation to 2
2011-05-10 07:03:28.791000 +02:00
Assigning activation ID 3146955065 (0xbb92b939)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO01.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
2011-05-10 07:03:31.229000 +02:00
Successfully onlined Undo Tablespace 2.
Dictionary check beginning
Tablespace 'TEMP' #3 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
*********************************************************************
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:

ALTER TABLESPACE ADD TEMPFILE

Alternatively, if these temporary tablespaces are no longer
needed, then they can be dropped.
Empty temporary tablespace: TEMP
*********************************************************************
Database Characterset is US7ASCII
Opening with internal Resource Manager plan
2011-05-10 07:03:32.932000 +02:00
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
If files cannot be cataloged, then manually delete them
using OS command.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
then disabled.
**********************************************************
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=19, OS id=3180
SMCO started with pid=20, OS id=2932
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-05-10 07:03:34.901000 +02:00
Starting background process QMNC
QMNC started with pid=21, OS id=3296
2011-05-10 07:03:35.995000 +02:00
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete
Global Name changed to HALIMDB
2011-05-10 07:03:47.338000 +02:00
Completed: alter database "halimdb" open resetlogs
alter database rename global_name to "halimdb"
Completed: alter database rename global_name to "halimdb"
ALTER TABLESPACE TEMP ADD TEMPFILE 'G:\app\Administrator\oradata\halimdb\TEMP01.
DBF' SIZE 20480K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
Completed: ALTER TABLESPACE TEMP ADD TEMPFILE 'G:\app\Administrator\oradata\hali
mdb\TEMP01.DBF' SIZE 20480K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
ALTER DATABASE DEFAULT TABLESPACE "USERS"
Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
ALTER SYSTEM disable restricted session;
2011-05-10 07:03:58.401000 +02:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-05-10 07:03:59.651000 +02:00
Starting background process CJQ0
CJQ0 started with pid=32, OS id=3624
2011-05-10 07:04:08.151000 +02:00
Full restore complete of datafile 5 to datafile copy G:\APP\ADMINISTRATOR\ORADAT
A\HALIMDB\EXAMPLE01.DBF. Elapsed time: 0:00:13
checkpoint is 905996
last deallocation scn is 905536
2011-05-10 07:04:11.713000 +02:00
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_j00
7_3364.trc:
ORA-12012: error on auto execute of job 11689
ORA-01403: no data found
2011-05-10 07:04:15.495000 +02:00
Plug in tablespace EXAMPLE with datafile
'G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\EXAMPLE01.DBF'
2011-05-10 07:04:39.041000 +02:00
ALTER TABLESPACE example READ WRITE
Completed: ALTER TABLESPACE example READ WRITE
2011-05-10 07:05:06.823000 +02:00
Stopping background process SMCO
Stopping background process FBDA
2011-05-10 07:05:07.901000 +02:00
Shutting down instance: further logons disabled
2011-05-10 07:05:10.573000 +02:00
Stopping background process QMNC
Stopping background process CJQ0
2011-05-10 07:05:12.588000 +02:00
Stopping background process MMNL
Stopping background process MMON
2011-05-10 07:05:17.682000 +02:00
Shutting down instance (immediate)
License high water mark = 11
Waiting for dispatcher 'D000' to shutdown
2011-05-10 07:05:19.713000 +02:00
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
SMON: disabling tx recovery
SMON: disabling cache recovery
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 1
Successful close of redo thread 1
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
2011-05-10 07:05:20.963000 +02:00
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
2011-05-10 07:05:22.010000 +02:00
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Stopping background process VKTM:
Archive process shutdown avoided: 0 active
2011-05-10 07:05:24.182000 +02:00
Instance shutdown complete
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in client-side pfile G:\APP\ADMINISTRATOR\CFGTOOLLOGS\D
BCA\HALIMDB\INITHALIMDBTEMP.ORA on machine XPSP3-WBB
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
_no_recovery_through_resetlogs= TRUE
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
PMON started with pid=2, OS id=1944
VKTM started with pid=3, OS id=2648 at elevated priority
DIAG started with pid=4, OS id=932
DBRM started with pid=5, OS id=2096
PSP0 started with pid=6, OS id=2668
DSKM started with pid=7, OS id=2656
DIA0 started with pid=8, OS id=1788
MMAN started with pid=9, OS id=2660
DBW0 started with pid=7, OS id=1760
LGWR started with pid=10, OS id=2328
CKPT started with pid=11, OS id=2712
SMON started with pid=12, OS id=2652
RECO started with pid=13, OS id=1720
MMON started with pid=14, OS id=1148
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = G:\app\Administrator
ALTER DATABASE MOUNT
2011-05-10 07:05:25.838000 +02:00
VKTM running at (20)ms precision
MMNL started with pid=15, OS id=2684
2011-05-10 07:05:32.151000 +02:00
Changing di2dbun from to halimdb
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 3146982327
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
ALTER DATABASE OPEN
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO01.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
2011-05-10 07:05:33.651000 +02:00
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is US7ASCII
Opening with internal Resource Manager plan
2011-05-10 07:05:34.745000 +02:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=18, OS id=196
SMCO started with pid=20, OS id=2364
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-05-10 07:05:36.979000 +02:00
Starting background process QMNC
QMNC started with pid=21, OS id=2064
2011-05-10 07:05:47.385000 +02:00
Completed: ALTER DATABASE OPEN
alter database character set INTERNAL_CONVERT WE8MSWIN1252
2011-05-10 07:05:52.573000 +02:00
Thread 1 advanced to log sequence 2
Current log# 2 seq# 2 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.LOG
2011-05-10 07:05:58.651000 +02:00
Updating character set in controlfile to WE8MSWIN1252
Synchronizing connection with database character set information
Refreshing type attributes with new character set information
2011-05-10 07:06:01.182000 +02:00
Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
ALTER SYSTEM disable restricted session;
2011-05-10 07:06:06.338000 +02:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-05-10 07:06:21.026000 +02:00
Stopping background process SMCO
Stopping background process FBDA
2011-05-10 07:06:22.041000 +02:00
Shutting down instance: further logons disabled
2011-05-10 07:06:27.041000 +02:00
Stopping background process QMNC
2011-05-10 07:06:29.041000 +02:00
Stopping background process MMNL
2011-05-10 07:06:30.041000 +02:00
Stopping background process MMON
2011-05-10 07:06:31.088000 +02:00
Shutting down instance (immediate)
License high water mark = 1
Waiting for dispatcher 'D000' to shutdown
2011-05-10 07:06:33.120000 +02:00
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
SMON: disabling tx recovery
SMON: disabling cache recovery
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 2
Successful close of redo thread 1
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
2011-05-10 07:06:34.229000 +02:00
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
2011-05-10 07:06:35.291000 +02:00
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Stopping background process VKTM:
Archive process shutdown avoided: 0 active
2011-05-10 07:06:37.432000 +02:00
Instance shutdown complete
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile G:\APP\ADMINISTRATOR\PRODUCT\11.1
.0\DB_1\DATABASE\SPFILEHALIMDB.ORA
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
VKTM started with pid=3, OS id=948 at elevated priority
PMON started with pid=2, OS id=1928
VKTM running at (20)ms precision
DIAG started with pid=4, OS id=1724
DBRM started with pid=5, OS id=3084
DSKM started with pid=7, OS id=1388
2011-05-10 07:06:38.401000 +02:00
PSP0 started with pid=6, OS id=2628
MMAN started with pid=7, OS id=3288
DIA0 started with pid=8, OS id=1660
2011-05-10 07:06:39.432000 +02:00
DBW0 started with pid=9, OS id=1956
LGWR started with pid=10, OS id=500
CKPT started with pid=11, OS id=2240
SMON started with pid=12, OS id=4076
RECO started with pid=13, OS id=1508
MMON started with pid=14, OS id=1932
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
MMNL started with pid=15, OS id=792
starting up 1 shared server(s) ...
ORACLE_BASE from environment = G:\app\Administrator
ALTER DATABASE MOUNT
2011-05-10 07:06:46.635000 +02:00
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 3146924546
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
ALTER DATABASE OPEN
Thread 1 opened at log sequence 2
Current log# 2 seq# 2 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
2011-05-10 07:06:47.995000 +02:00
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
2011-05-10 07:06:49.635000 +02:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=18, OS id=2216
SMCO started with pid=20, OS id=2204
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-05-10 07:06:51.073000 +02:00
Starting background process QMNC
QMNC started with pid=21, OS id=3180
2011-05-10 07:06:59.010000 +02:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-05-10 07:07:05.932000 +02:00
Completed: ALTER DATABASE OPEN
2011-05-10 07:07:15.182000 +02:00
Starting background process CJQ0
CJQ0 started with pid=34, OS id=3220
2011-05-10 07:07:29.385000 +02:00
Thread 1 advanced to log sequence 3
Current log# 3 seq# 3 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO03.LOG
2011-05-10 07:11:52.026000 +02:00


***********************************************************************

Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.1.0.6.0 - Pro
duction
Time: 10-MAY-2011 07:11:52
Tracing not turned on.
Tns error struct:
ns main err code: 12638

TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
2011-05-10 07:13:20.531000 +02:00
Starting ORACLE instance (normal)
2011-05-10 07:13:23.375000 +02:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
2011-05-10 07:13:24.656000 +02:00
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
2011-05-10 07:13:27.203000 +02:00
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile G:\APP\ADMINISTRATOR\PRODUCT\11.1
.0\DB_1\DATABASE\SPFILEHALIMDB.ORA
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
2011-05-10 07:13:28.656000 +02:00
PMON started with pid=2, OS id=2164
VKTM started with pid=3, OS id=2168 at elevated priority
VKTM running at (20)ms precision
DIAG started with pid=4, OS id=2172
DBRM started with pid=5, OS id=2176
PSP0 started with pid=6, OS id=2180
DSKM started with pid=7, OS id=2184
DIA0 started with pid=8, OS id=2188
MMAN started with pid=9, OS id=2192
DBW0 started with pid=10, OS id=2196
LGWR started with pid=11, OS id=2200
CKPT started with pid=12, OS id=2204
SMON started with pid=13, OS id=2208
RECO started with pid=14, OS id=2212
MMON started with pid=15, OS id=2216
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
MMNL started with pid=16, OS id=2220
starting up 1 shared server(s) ...
ORACLE_BASE from environment = G:\app\Administrator
2011-05-10 07:13:30.625000 +02:00
alter database mount exclusive
2011-05-10 07:13:37.906000 +02:00
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 3146947741
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
2011-05-10 07:13:39.968000 +02:00
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
2011-05-10 07:13:43.171000 +02:00
Started redo scan
2011-05-10 07:13:44.656000 +02:00
Completed redo scan
33382 redo blocks read, 2368 data blocks need recovery
2011-05-10 07:13:46.578000 +02:00
Started redo application at
Thread 1: logseq 2, block 89996
Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0
Mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.LOG
2011-05-10 07:13:49.796000 +02:00
Recovery of Online Redo Log: Thread 1 Group 3 Seq 3 Reading mem 0
Mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO03.LOG
2011-05-10 07:13:51.609000 +02:00
Completed redo application
Completed crash recovery at
Thread 1: logseq 3, block 26288, scn 955632
2368 data blocks read, 2368 data blocks written, 33382 redo blocks read
2011-05-10 07:13:54.718000 +02:00
Thread 1 advanced to log sequence 4
Thread 1 opened at log sequence 4
Current log# 1 seq# 4 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO01.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
2011-05-10 07:14:02.062000 +02:00
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
2011-05-10 07:14:03.265000 +02:00
Database Characterset is WE8MSWIN1252
2011-05-10 07:14:06.125000 +02:00
Opening with internal Resource Manager plan
2011-05-10 07:14:09.468000 +02:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=21, OS id=2456
SMCO started with pid=22, OS id=2460
2011-05-10 07:14:10.531000 +02:00
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-05-10 07:14:15.234000 +02:00
Starting background process QMNC
QMNC started with pid=24, OS id=2504
2011-05-10 11:14:24.734000 +02:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-05-10 11:15:11.140000 +02:00
Completed: alter database open
2011-05-10 11:17:05.515000 +02:00
Starting background process CJQ0
CJQ0 started with pid=19, OS id=1880
Stopping background process CJQ0
[YOURAPP] A Critical error was detected in module: INIT
2011-05-10 15:22:20.593000 +06:00
Warning! your DB need Restart now
2011-05-10 15:24:36.812000 +06:00
Warning! your DB need Restart now
2011-05-10 15:25:11.734000 +06:00
Warning! your DB need Restart now
2011-05-10 15:47:16.812000 +06:00
Starting background process CJQ0
CJQ0 started with pid=19, OS id=2608
2011-05-11 02:00:00.187000 +06:00
Setting Resource Manager plan SCHEDULER[0x2C0A]:DEFAULT_MAINTENANCE_PLAN via sch
eduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
2011-05-11 02:00:03.608000 +06:00
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TU
NING_TASK"
Wed May 11 02:00:04 2011
Logminer Bld: Lockdown Complete. DB_TXN_SCN is UnwindToSCN (LockdownSCN) is 9
92685
2011-05-11 02:01:30.280000 +06:00
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNI
NG_TASK"
2011-05-11 02:01:35.655000 +06:00
Thread 1 advanced to log sequence 5
Current log# 2 seq# 5 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.LOG
2011-05-11 06:00:00.124000 +06:00
Clearing Resource Manager plan via parameter
2011-05-11 10:27:27.062000 +06:00


***********************************************************************

Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.1.0.6.0 - Pro
duction
Time: 11-MAY-2011 10:27:27
Tracing not turned on.
Tns error struct:
ns main err code: 12638

TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
2011-05-16 11:01:52.953000 +06:00
Starting ORACLE instance (normal)
2011-05-16 11:02:02.765000 +06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
2011-05-16 11:02:04.296000 +06:00
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
2011-05-16 11:02:05.312000 +06:00
SYS auditing is disabled
2011-05-16 11:02:06.875000 +06:00
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile G:\APP\ADMINISTRATOR\PRODUCT\11.1
.0\DB_1\DATABASE\SPFILEHALIMDB.ORA
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
2011-05-16 11:02:07.984000 +06:00
PMON started with pid=2, OS id=1480
VKTM started with pid=3, OS id=1064 at elevated priority
DIAG started with pid=4, OS id=2524
VKTM running at (20)ms precision
DBRM started with pid=5, OS id=2144
PSP0 started with pid=6, OS id=1844
DSKM started with pid=7, OS id=3196
DIA0 started with pid=8, OS id=1112
MMAN started with pid=9, OS id=2024
DBW0 started with pid=10, OS id=1548
LGWR started with pid=11, OS id=1468
CKPT started with pid=12, OS id=2608
SMON started with pid=13, OS id=1352
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
MMON started with pid=15, OS id=3716
starting up 1 shared server(s) ...
ORACLE_BASE from environment = G:\app\Administrator
RECO started with pid=14, OS id=3888
MMNL started with pid=16, OS id=2520
2011-05-16 11:02:10.484000 +06:00
alter database mount exclusive
2011-05-16 11:02:16.875000 +06:00
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 3147457331
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
2011-05-16 11:02:18.453000 +06:00
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Started redo scan
2011-05-16 11:02:19.906000 +06:00
Completed redo scan
69 redo blocks read, 26 data blocks need recovery
Started redo application at
Thread 1: logseq 5, block 64372
Recovery of Online Redo Log: Thread 1 Group 2 Seq 5 Reading mem 0
Mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.LOG
Completed redo application
Completed crash recovery at
Thread 1: logseq 5, block 64441, scn 1049886
26 data blocks read, 26 data blocks written, 69 redo blocks read
2011-05-16 11:02:21.718000 +06:00
Thread 1 advanced to log sequence 6
Thread 1 opened at log sequence 6
Current log# 3 seq# 6 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO03.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
2011-05-16 11:02:25.828000 +06:00
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
2011-05-16 11:02:27.296000 +06:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=21, OS id=2224
SMCO started with pid=22, OS id=164
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-05-16 11:02:29.578000 +06:00
Starting background process QMNC
QMNC started with pid=23, OS id=3328
2011-05-16 11:02:40.750000 +06:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-05-16 11:02:50.421000 +06:00
Completed: alter database open
2011-05-16 11:07:11.796000 +06:00
Starting background process CJQ0
CJQ0 started with pid=27, OS id=3828
2011-05-16 11:12:33.171000 +06:00
ALTER SYSTEM SET smtp_out_server='10.11.1.40:25' SCOPE=BOTH;
2011-05-16 20:38:36.406000 +06:00
Thread 1 advanced to log sequence 7
Current log# 1 seq# 7 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO01.LOG
2011-05-17 02:00:00.156000 +06:00
Setting Resource Manager plan SCHEDULER[0x2C09]:DEFAULT_MAINTENANCE_PLAN via sch
eduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
2011-05-17 02:00:03.671000 +06:00
Tue May 17 02:00:03 2011
Logminer Bld: Lockdown Complete. DB_TXN_SCN is UnwindToSCN (LockdownSCN) is 1
094261
2011-05-17 02:00:05.578000 +06:00
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TU
NING_TASK"
2011-05-17 02:00:59.046000 +06:00
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNI
NG_TASK"
2011-05-17 06:00:00.109000 +06:00
Clearing Resource Manager plan via parameter
2011-05-17 09:39:38.109000 +06:00
Thread 1 advanced to log sequence 8
Current log# 2 seq# 8 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.LOG
2011-05-17 11:59:07.234000 +06:00


***********************************************************************

Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.1.0.6.0 - Pro
duction
Time: 17-MAY-2011 11:59:07
Tracing not turned on.
Tns error struct:
ns main err code: 12638

TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
2011-05-18 18:10:23.032000 +06:00
Starting ORACLE instance (normal)
2011-05-18 18:10:25.392000 +06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
2011-05-18 18:10:26.657000 +06:00
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
2011-05-18 18:10:27.751000 +06:00
SYS auditing is disabled
2011-05-18 18:10:29.079000 +06:00
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile G:\APP\ADMINISTRATOR\PRODUCT\11.1
.0\DB_1\DATABASE\SPFILEHALIMDB.ORA
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
smtp_out_server = "10.11.1.40:25"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
2011-05-18 18:10:30.282000 +06:00
PMON started with pid=2, OS id=2660
VKTM started with pid=3, OS id=3836 at elevated priority
DIAG started with pid=4, OS id=3604
VKTM running at (20)ms precision
PSP0 started with pid=6, OS id=3832
DBRM started with pid=5, OS id=2992
DIA0 started with pid=8, OS id=3276
DSKM started with pid=7, OS id=1832
MMAN started with pid=9, OS id=2124
DBW0 started with pid=10, OS id=1200
LGWR started with pid=11, OS id=2836
CKPT started with pid=12, OS id=2296
SMON started with pid=13, OS id=468
RECO started with pid=14, OS id=1640
MMON started with pid=15, OS id=880
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
MMNL started with pid=16, OS id=1684
starting up 1 shared server(s) ...
2011-05-18 18:10:31.704000 +06:00
ORACLE_BASE from environment = G:\app\Administrator
2011-05-18 18:10:32.892000 +06:00
alter database mount exclusive
2011-05-18 18:10:38.157000 +06:00
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 3147670937
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
2011-05-18 18:10:39.314000 +06:00
parallel recovery started with 2 processes
2011-05-18 18:10:40.517000 +06:00
Started redo scan
Completed redo scan
84 redo blocks read, 24 data blocks need recovery
2011-05-18 18:10:42.204000 +06:00
Started redo application at
Thread 1: logseq 8, block 10632
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
Mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO02.LOG
Completed redo application
2011-05-18 18:10:43.470000 +06:00
Completed crash recovery at
Thread 1: logseq 8, block 10716, scn 1153835
24 data blocks read, 24 data blocks written, 84 redo blocks read
2011-05-18 18:10:45.736000 +06:00
Thread 1 advanced to log sequence 9
Thread 1 opened at log sequence 9
Current log# 3 seq# 9 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO03.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
2011-05-18 18:10:48.861000 +06:00
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
2011-05-18 18:10:51.579000 +06:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=21, OS id=1060
SMCO started with pid=22, OS id=1372
2011-05-18 18:10:52.736000 +06:00
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-05-18 18:10:53.986000 +06:00
Starting background process QMNC
QMNC started with pid=23, OS id=3856
2011-05-18 18:11:08.157000 +06:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-05-18 18:11:17.501000 +06:00
Completed: alter database open
2011-05-18 18:15:36.329000 +06:00
Starting background process CJQ0
CJQ0 started with pid=27, OS id=1832
2011-05-18 18:45:03.564000 +06:00


***********************************************************************

Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.1.0.6.0 - Pro
duction
Time: 18-MAY-2011 18:45:03
Tracing not turned on.
Tns error struct:
ns main err code: 12638

TNS-12638: Credential retrieval failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
2011-06-14 11:59:57.031000 +06:00
Starting ORACLE instance (normal)
2011-06-14 11:59:58.937000 +06:00
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as G:\app\Administrator\product
\11.1.0\db_1\RDBMS
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
2011-06-14 11:59:59.921000 +06:00
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
2011-06-14 12:00:02.515000 +06:00
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile G:\APP\ADMINISTRATOR\PRODUCT\11.1
.0\DB_1\DATABASE\SPFILEHALIMDB.ORA
System parameters with non-default values:
processes = 150
memory_target = 1012M
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL01.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL02.CTL
"
control_files = "G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\CONTROL03.CTL
"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "G:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=halimdbXDB)"
smtp_out_server = "10.11.1.40:25"
audit_file_dest = "G:\APP\ADMINISTRATOR\ADMIN\HALIMDB\ADUMP"
audit_trail = "DB"
db_name = "halimdb"
open_cursors = 300
diagnostic_dest = "G:\APP\ADMINISTRATOR"
2011-06-14 12:00:03.718000 +06:00
PMON started with pid=2, OS id=3916
VKTM started with pid=3, OS id=1816 at elevated priority
DIAG started with pid=4, OS id=1060
DBRM started with pid=5, OS id=2808
PSP0 started with pid=6, OS id=3304
DSKM started with pid=7, OS id=3404
DIA0 started with pid=8, OS id=4004
MMAN started with pid=9, OS id=3828
DBW0 started with pid=10, OS id=2572
CKPT started with pid=12, OS id=3740
LGWR started with pid=11, OS id=232
SMON started with pid=13, OS id=1904
RECO started with pid=14, OS id=1716
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
MMON started with pid=15, OS id=1532
starting up 1 shared server(s) ...
ORACLE_BASE from environment = G:\app\Administrator
2011-06-14 12:00:04.781000 +06:00
VKTM running at (20)ms precision
MMNL started with pid=16, OS id=1492
alter database mount exclusive
2011-06-14 12:00:11.562000 +06:00
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 3150041927
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
2011-06-14 12:00:12.703000 +06:00
parallel recovery started with 2 processes
2011-06-14 12:00:13.734000 +06:00
Started redo scan
2011-06-14 12:00:14.828000 +06:00
Completed redo scan
18257 redo blocks read, 1236 data blocks need recovery
2011-06-14 12:00:16.453000 +06:00
Started redo application at
Thread 1: logseq 9, block 4610
Recovery of Online Redo Log: Thread 1 Group 3 Seq 9 Reading mem 0
Mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO03.LOG
2011-06-14 12:00:17.968000 +06:00
Completed redo application
Completed crash recovery at
Thread 1: logseq 9, block 22867, scn 1178420
1236 data blocks read, 1236 data blocks written, 18257 redo blocks read
2011-06-14 12:00:19.390000 +06:00
Thread 1 advanced to log sequence 10
Thread 1 opened at log sequence 10
Current log# 1 seq# 10 mem# 0: G:\APP\ADMINISTRATOR\ORADATA\HALIMDB\REDO01.LOG

Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
2011-06-14 12:00:22.078000 +06:00
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
2011-06-14 12:00:23.562000 +06:00
Starting background process FBDA
Starting background process SMCO
FBDA started with pid=21, OS id=1244
SMCO started with pid=22, OS id=3472
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
2011-06-14 12:00:25.609000 +06:00
Starting background process QMNC
QMNC started with pid=23, OS id=4052
2011-06-14 12:00:36.796000 +06:00
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
2011-06-14 12:00:48.359000 +06:00
Completed: alter database open
2011-06-14 12:05:07.578000 +06:00
Starting background process CJQ0
CJQ0 started with pid=7, OS id=1748
2011-06-14 12:05:18.171000 +06:00
Errors in file g:\app\administrator\diag\rdbms\halimdb\halimdb\trace\halimdb_j00
9_2164.trc:
ORA-12012: error on auto execute of job 11689
ORA-01403: no data found
adrci>
adrci>
adrci> SHOW TRACEFILE
diag\rdbms\halimdb\halimdb\trace\alert_halimdb.log
diag\rdbms\halimdb\halimdb\trace\halimdb_cjq0_2608.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_cjq0_3828.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_dbrm_2096.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_dbrm_2144.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_dbrm_2176.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_dbrm_2808.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_dbrm_2992.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_dbrm_3084.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_dbrm_4064.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j001_2268.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j001_3276.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j003_2616.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j004_3288.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j005_3412.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j005_3744.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j007_3364.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_j009_2164.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1044.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1340.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1344.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1464.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1484.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1596.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1640.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1676.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_168.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1744.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1824.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_1992.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2008.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2028.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2136.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2148.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2196.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2364.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2372.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2424.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2816.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2992.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_2996.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3120.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3124.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3168.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3196.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3508.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3544.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3592.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3648.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3664.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3764.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3784.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3860.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3876.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_388.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3900.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_3960.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_4016.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_4036.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_632.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_668.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_776.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_876.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m000_968.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m001_3080.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m001_4084.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m001_644.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_m001_776.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_1388.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_1744.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_1780.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_1812.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_1992.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2056.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2088.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2172.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2180.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2196.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2208.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2252.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2364.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2392.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2412.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2604.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2720.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2776.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2856.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2888.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_2980.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_3048.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_3180.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_3648.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_4008.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_4084.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_4092.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_424.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_ora_976.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p000_2320.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p000_2976.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p000_3488.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p000_428.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p001_1456.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p001_2276.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p001_2324.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_p001_2688.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_q001_2520.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_1064.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_1816.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_2168.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_2624.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_2648.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_2936.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_3836.trc
diag\rdbms\halimdb\halimdb\trace\halimdb_vktm_948.trc
adrci>
adrci>
adrci> SHOW TRACEFILE -I 1681
adrci>
adrci> SHOW TRACEFILE -I 948
adrci>
adrci> SHOW INCIDENT

ADR Home = g:\app\administrator\diag\rdbms\halimdb\halimdb:
*************************************************************************
0 rows fetched

adrci>