Some Question and Answar about oracle database licensing

Collected from various source only for my self for answering the questions about oracle licensing .----------------------------------------------------------------------------

Q: What is the difference between Oracle Standard Edition and Oracle Standard Edition One?

A: There are two differences. Firstly, Oracle Standard Edition One can only be licensed on servers that have a maximum capacity of 2 processors (CPUs). If your server has a maximum capacity of 3 processors or more then you will have to purchase Oracle Standard Edition (or if it has a maximum capacity of more than 4 processors, you will have to purchase Oracle Enterprise Edition). Secondly, Oracle Standard Edition One does not support clustering whereas Oracle Standard Edition includes Oracle Real Application Clusters.

Q: I only use 2 processors on my server, but it can support 4 processors. Do I still need to purchase Oracle Standard Edition rather than Oracle Standard Edition One?

A: Yes. Your eligibility to use Oracle Standard Edition One is not determined by how many processors are in place or in use, but by how many processors the server has capacity for.

Q: I would like to cluster my servers. Which license level should I choose?

A: This depends on how many processors there are in your cluster. If you have 4 or less then you can purchase either Oracle Standard Edition or Oracle Enterprise Edition licenses. If you have 4 or more processors in total across the cluster then you must choose Oracle Enterprise Edition. Oracle RAC (Real Application Clusters) is a licensing option for Oracle Enterprise Edition.

Q: Are there any minimum order requirements when purchasing Named User database licenses?

A: Yes. The minimum order requirements vary depending on which database product you select. These are:
Standard Edition One - 5 Named User Plus licenses per server or the total number of actual users, whichever is greater.
Standard Edition - 5 Named User Plus licenses per server or the total number of actual users, whichever is greater.
Enterprise Edition - 25 Named User Plus licenses per processor or the total number of actual users, whichever is greater.
Personal and Lite Editions - 1 Named User Plus license or the total number of actual users, whichever is greater.

Q: Do I need to buy Named User Plus or per Processor licenses?

A: If you select the Named User Plus licensing option then you must license all the users who are using the Oracle Database, as well as all non-human operated devices accessing the Oracle Database. An example of a non-human device would be a sensor that connects to a database. If a human-operated device such as a bar code scanner connects to the database then all humans operating these devices need to be licensed. If the Named User Plus population is likely to be very high, it would be more cost effective to license per processor. Where it is impossible to quantify the user population (such as in an Internet environment), then you must license per processor.

Q: My server contains multi-core processors. How do I price this?

A: For Standard Edition and Standard Edition One, the number of cores can be ignored (an occupied socket is equivalent to one processor for these editions). For Enterprise Edition, each core of a multi-core chip is priced using a "licensing factor". These licensing factors are as follows:
Sun UltraSPARC T1 - 0.25
AMD/Intel - 0.5
All other multi-core processors - 0.75
Single core processors - 1
Therefore if you have two dual-core AMD Opteron processors, the cost will be 0.5*4*list price. Two four-core UltraSPARC T1 processors will cost 0.25*8*list price.

Q: Do multi-core processors affect the processor limits on Oracle Standard Edition and Oracle Standard Edition One?

A: No. Oracle Standard Edition can only be used on servers that have a maximum capacity of 4 processors (CPUs), regardless of the number of cores. In a RAC environment, this limitation applies to the whole cluster (i.e. the total number of processors in the cluster must be less than or equal to 4).
Oracle Standard Edition One can only be used on servers that have a maximum capacity of 2 processors.

Q: Can you offer me a discount on Oracle list prices?

A: Yes. Please contact us with your requirements and we will advise you on the level of discount we can offer.

Q: Once I have placed my order how long will I have to wait for my license details?

A: Your order is logged with Oracle who then issue us with a license number for you. This process can take up to 10 business days.

Q: What are your payment terms?

A: Payment is due within 30 days of the invoice date (subject to approval). For larger orders or maximum discounts, payment-on-order is required.

Multi-core Processors: Impact On Oracle Processor Licensing

Q: How does Oracle price its software?

A: For its technology products, Oracle has two primary pricing models. Customers can choose between Named User Plus and Per Processor pricing models based on their specific needs. Named User Plus is ideal for organizations with discrete and countable user populations. For uncountable populations, processor licensing is required. The Processor pricing model is based on the number of processors a customer has installed and the number of those processors that the customer has operating. This model is easily measured, a fact that makes costs transparent for our customers.

Q: Why did Oracle change its multi-core pricing?

A: The goal of Oracle's pricing and licensing strategy is to provide simple and flexible licensing models to meet our customers' needs. For the past several months, we have been working closely with our customers and hardware Partners to address the recent advancements in multicore processor chips. To meet these needs, Oracle is changing its licensing policy regarding multi-core chips. Our first change to address multi-core technology occurred in July 2005 and further changes as described below became effective on December 19, 2005.

Q: What is the new multi-core pricing and licensing model?

Oracle will continue to recognize each core as a separate processor; however, the processor definition has been amended when counting multi-core chips when determining the total number of processor licenses required. Prior to this update, there were two categories for processor licensing. With this update, we are introducing two additional processor categories. As a result, there are four categories for processor licensing. Each category has a unique processor-pricing factor, which is used to determine the total number of processor licenses required.

Oracle Processor Licensing:

Cores Processor Factor CPUs for SW Licenses

UltraSPARC T1 8 0.25 2

AMD/Intel 4 0.50 2

All other Multi-core Chips (IBM Pseries, SM USIV, etc.) 2 0.75 2

Single Core Servers 1 1.00 1

To find the total number of processors, which require licensing, for a Sun UltraSPARC T1 processor with 4, 6 or 8 cores at 1.0 gigahertz or 8 cores at 1.2 gigahertz for only those servers specified on the Sun Server Table which can be accessed at http://oracle.com/contracts, “n” cores

shall be determined by multiplying the total number of cores by a factor of .25. For the purposes

of counting the number of processors which require licensing for AMD and Intel multi-core chips, “n” cores shall be determined by multiplying the total number of cores by a factor of .50. For the purposes of counting the number of processors which require licensing for all hardware platforms not otherwise specified in this section, a multi-core chip with "n" cores shall be determined by multiplying "n" cores by a factor of .75. All cores on all multi-core chips for each licensed program for each factor listed below are to be aggregated before multiplying by the appropriate factor and all fractions of a number are to be rounded up to the next whole number. Notwithstanding the above, when licensing Oracle Standard Edition One or Standard Edition programs on servers with a maximum of 1 processor with 1 or 2 cores, only 1 processor shall be counted.

For example, an 8–way p5 570 Server from IBM is actually a 4-way dual core server. The server has four chips with 8 physical processors. Prior to our multi-core licensing changes, this server had a list license price of $320,000 (4*2 [cores] *$40,000).

Based on the updated licensing methodology, this IBM server’s software licensing fees will be $240,000 (0.75 * 8 *$40,000), which is a price decrease of 25%.

Other examples:

A Sun Fire T2000 Server with one 1.2 GHz UltraSPARC T1 processor (with 8 cores) will

require 8*0.25 = 2 Processor licenses

A Sun Fire T2000 Server with one 1.2 GHz UltraSPARC T1 processor (with 4 cores) will

require 4*0.25 = 1 Processor licenses with a total list license price of $40,000

An HP ProLiant DL145 G2 with two AMD Opteron 200 Series dual-core processors Model 280

will require 2*2*0.5 = 2 processor licenses with total list license fee of $80,000

Licensing our database software by processor is one of several choices we provide to our

customers. As mentioned earlier, other options include licensing per user and per employee. Oracle also offers the option of licensing its software on a perpetual or term basis (1-year, 2-year, 3-year, 4-year and 5-year).

Q: Do the multicore processor licensing changes impact how Oracle Database Standard

Edition and Standard Edition One are calculated?

A: Yes. According to the latest amendment to the hardware-licensing requirement for Database SE and SE One programs, the following policy applies:

Oracle Database Standard Edition can only be licensed on servers that have a maximum capacity of 4 single core processors cores. For multicore chips, the maximum number of cores per server is determined by multiplying the core processor licensing factors (as contained in the processor definition) by the number of cores. The result must be less than or equal to 4 and the total number of cores must be less than or equal to 8.

When using RAC to cluster this limitation is mirrored in the cluster. It may be licensed on a single cluster of servers supporting up to a maximum of four single-core processors cores per cluster (2 2-way nodes, 4 1-way nodes, and 1 1-way and 1 3-way). For multicore chips, the maximum number of cores per cluster is determined by multiplying the core processor licensing factors (as contained in the processor definition) by the number of cores. The result must be less than or equal to 4 and the total number of cores in the cluster must be less than or equal to 8. For SE One programs: Oracle Standard Edition One may only be licensed on servers that have a maximum capacity of 2 single core processors cores. For multicore chips, the maximum number of cores per server is determined by multiplying the core processor licensing factors (as contained in the processor definition) by the number of cores. The result must be less than or equal to 2 and the total number of cores must be less than or equal to 4 Note that this change is retroactive and applies to all customers licensed for these programs previously.

Examples - For illustrative purposes only:

Sun Fire T2000 Server with one 1.2 GHz UltraSPARC T1 processor (with 8 cores) will require 8*0.25 = 2 Processor licenses. This model is eligible for licensing Database Standard Edition. It is not eligible for licensing DB SE One as the total number of cores on this server exceeds the maximum permitted, which are 4 for SE One.

Sun Fire T2000 Server with one 1.2 GHz UltraSPARC T1 processor (with 4 cores) will require 4*0.25 = 1 Processor licenses. This model is eligible for licensing Database Standard Edition One, as the total number of cores in this server is 4, which is the maximum permissible for licensing SE One.

Dell PowerEdge 2850 with two dual-core Intel Xeon Processors will require 2*2*0.5 = 2

Processor licenses. This model is eligible for licensing Database Standard Edition One.

HP ProLiant DL145 G2 with two AMD Opteron 200 Series dual-core processors Model 280

will require 2*2*0.5 = 2 processor license. This model is eligible for licensing Database Standard Edition One.

Q: Does that mean that Oracle’s software prices will increase for customers using dualcore processors?

A: No. Oracle’s software pricing per processor has not increased for customers using dual core processors. The effective price per processor has decreased. Many hardware industry experts state that dual core processors yield 1.5 to 1.75 times the performance of a single core processor, but do not yield twice the performance of single core processors. Oracle’s dual core pricing is a factor of 0.75 of a single core, which is effectively a 25% decrease for processor based licenses with the dual core technology. For Intel and AMD based multi-core chips this factor is 0.50 and for SUN’s UltraSPARC T1 multi-core chips this factor is 0.25.

Additionally, for the purpose of managing processor licenses, customers can also partition their servers and run Oracle on a subset of the processor cores within a server. This facilitates the customer’s ability to efficiently manage their software licenses and only pay for those that are employed for the purpose of running Oracle’s software. More information on Partitioning is located at http://www.oracle.com/corporate/pricing/partitioning.pdf

Q: Does Oracle charge for multithreading or have specific pricing for multithreading?

A: No, Oracle does not charge for multithreading. A processor core is a set of one or more processor threads. The processor thread tracks execution of a software program thread. As a result, Oracle does not charge per number of threads.

Q: How do Oracle competitors (like IBM and Microsoft) treat pricing for multi-core chips?

A: There are slight differences in the manner in which each database software vendor handles dual core pricing and licensing. For example, IBM treats each core as a separate CPU for their eServer pSeries products. For Intel x86 servers, they license per socket. Microsoft, whose installed base is primarily licensed using their user based metric of “client access license” when licensing via the processor metric, like IBM also counts each socket, regardless of the number of cores. SQL Server does not run in Unix environments.

Q: How does the new pricing affect an existing customer?

A: All customers are eligible for the new licensing. No new contracts are regarded, nor are any migrations needed to take advantage of the new licensing changes.

Q: How does Oracle see licensing models evolving over the next couple of years?

A: Software licensing models evolve as IT environments continue to evolve. Driven by the propagation of n-tier architectures, our current licensing models grew from concurrent user, named user single server and named user multi-server licensing models to processor and named user plus models. As the software landscape continues to transform, we anticipate that software licensing will continue to transform along with it.

Some useful link:-

http://www.oracle.com/us/corporate/pricing/price-lists/index.html

http://www.oracle.com/us/corporate/contracts/processor-core-factor-table-070634.pdf

1) you can find information about about oracle license

select * from v$license;

2) you can find information about install products in your database

Select decode(detected_usages,0,2,1) nop,

       name, version, detected_usages, currently_used,

       to_char(first_usage_date,'DD/MM/YYYY') first_usage_date, 

       to_char(last_usage_date,'DD/MM/YYYY') last_usage_date

from dba_feature_usage_statistics

order by nop, 1, 2

/

we use umask 022 on linux profile when oracle database installation but why?

we use umask 022 but why?

The octal umasks are calculated via the bitwise AND of the unary complement of the argument using bitwise NOT. The octal notations are as follows:

• Octal value : Permission
• 0 : read, write and execute
• 1 : read and write
• 2 : read and execute
• 3 : read only
• 4 : write and execute
• 5 : write only
• 6 : execute only
• 7 : no permissions

so A umask of 022 allows only you to write data, but anyone can read and execute data.

Oracle Database Performance (tuning) Monitoring Tools

Oracle Database Performance Monitoring Tools

A quick attention to available tools that can be used for resolving oracle Database performance issue.

Query Tuning

Enterprise Manager (SQL Tuning Advisor)	The SQL Tuning Advisor is a feature included with the EM Tuning Pack for Oracle 10g or higher. The SQL Tuning Advisor takes one or more SQL statements as an input and invokes the Automatic Tuning Optimizer to perform SQL tuning on the statements. The output of the SQL Tuning Advisor is in the form of an advice or recommendations, along with a rationale for each recommendation and its expected benefit. The recommendation relates to collection of statistics on objects, creation of new indexes, restructuring of the SQL statement, or creation of SQL Profile. NOTE: The EM Tuning Pack is a separately licensed product.
AWR SQL Report (awrsqrpt.sql)	The AWR SQL reporting utility is used to focus on the historical performance of a single SQL statement (identified by SQL_ID). It will tell you performance statistics and execution plans for each execution within a specified period (even if the statement had different child cursors). The awrsqrpt.sql script is found in the $ORACLE_HOME/rdbms/admin directory. Please note you must have a license to use this script.
SQLTXPLAIN	SQLTXPLAIN is a tool that generates a comprehensive report about a SQL statement which has been provided as input to the tool. The report includes the explain plan for a given SQL statement, cost-based optimizer statistics for the objects accessed by the statement, and details of related objects. The output HTML report produced can be used to analyze and diagnose SQL performance issues (SQL tuning).
TRCANLZR	TRCANLZR (Trace Analyzer) reads a raw SQL Trace generated by standard SQL Trace or by EVENT 10046 (Level 4, 8 or 12), and generates a comprehensive HTML report with performance related details: time summary, call summary (parse, execute, fetch), identification of top SQL, row source plan, explain plan, CBO statistics, wait events, values of bind variables, I/O summary per schema object, latches, hot blocks, etc. The Output HTML report includes all the details found on TKPROF, plus additional information normally requested and used for a transaction performance analysis. Generated report is more readable and extensive than text format used on prior version of this tool and on current TKPROF.
PL/SQL Profiler	PL/SQL Profiler is useful when there is a significant gap between user elapsed time and SQL processing elapsed time, and there is PL/SQL code involved. The PL/SQL Profiler is a very useful tool to help identify the lines of PL/SQL code which are responsible for taking the most time.
LTOM (Session Trace Collector)	The Lite Onboard Monitor (LTOM) is a java program designed as a real-time diagnostic platform for deployment to a customer site. LTOM is proactive rather than reactive and provides real-time automatic problem detection and data collection. LTOM runs on the customer's UNIX server, is tightly integrated with the host operating system and provides an integrated solution for detecting and collecting trace files for system performance issues. When troubleshooting query performance, the Automatic Session Tracing feature for LTOM can be used. LTOM's Automatic Session Tracing feature uses a set of rules to determine when to turn on SQL trace for individual Oracle sessions, using event 10046 level 12 trace. Rules can be defined for database wait events, CPU and specific users. When tracing directly to a file, automatic session tracing simply turns on tracing automatically for any session which violates the rule definitions. When exiting automatic session tracing all sessions currently being traced will have their respective tracing turned off.
OPDG	Oracle Performance Diagnostic Guide is intended to help resolve query tuning, hang/locking, and slow database issues. The guide is not an automated tool but rather seeks to show methodologies, techniques, common causes, and solutions to performance problems.

Os Tuning

When troubleshooting performance issues, it is helpful to gather and examine OS related data. Use the below tool to gather data specific to the OS.

OS Watcher

OSW is a series of shell scripts that collect specific kinds of data, using Unix operating system diagnostic utilities. Control is passed to individually spawned operating system data collector processes, which in turn collect specific data, timestamp the data output, and append the data to pre-generated and named files. Each data collector will have its own file, created and named by the File Manager process. OSW invokes the distinct operating system utilities listed below as data collectors. These utilities will be supported, or their equivalents, as available for each supported target platform. ps top mpstat iostat netstat traceroute vmstat

Database Tuning

A slow database or performance issue can manifest itself as:

· A large number of sessions that run slower than usual.

· The database permits logons and seems to be working (not hung) but takes much longer than usual to show results.

· Many different types of activity all slow down at around the same time.

Use these utilities for collecting data or diagnosing cluster or instance-wide database performance issues.

Enterprise Manager Automatic Diagnostic Database Monitor (ADDM)	The Automatic Database Diagnostic Monitor (ADDM) provides a holistic tuning solution. ADDM analysis can be performed over any time period defined by a pair of AWR snapshots taken on a particular instance. Analysis is performed top down, first identifying symptoms and then refining them to reach the root causes of performance problems.
ADDM Report (addmrpt.sql)	The ADDM reporting utility creates a report of its database performance findings. The addmrpt.sql script is found in the $ORACLE_HOME/rdbms/admin directory. Please note you must have a license to use this script.
Statspack (spreport.sql)	The Statspack reporting utility provides an overview of database performance within a specified period of time. It essentially computes the net change in database activity within the period. The spreport.sql script is found in the $ORACLE_HOME/rdbms/admin directory. You must install the statspack tables and package before using it by running spcreate.sql (see spdoc.txt). You do not need an additional license to use statspack.
AWR Report (awrrpt.sql)	The AWR reporting utility provides an overview of database performance within a specified period of time. It essentially computes the net change in database activity within the period. The awrrpt.sql script is found in the $ORACLE_HOME/rdbms/admin directory. Please note you must have a license to use this script.
RDA (DBPERF Profile)	Remote Diagnostic Agent (RDA) is a set of command line diagnostic scripts that are executed by an engine written in the Perl programming language. RDA is used to gather detailed information about an Oracle environment; the data gathered is in turn used to aid in problem diagnosis. The output is also useful for seeing the overall system configuration. Oracle Support encourages the use of RDA because it provides a comprehensive picture of the customer's environment. This can greatly reduce service request resolution time by minimizing the number of requests from Oracle Customer Support for more information. RDA is designed to be as unobtrusive as possible; it does not modify systems in any way, it only collects useful data for Oracle Customer Support. RDA can be executed using a setup profile. A setup profile consists of a list of data collection modules and predefined settings. Therefore, the data collected using a profile can be slightly different than using the module separately. Profiles are typically used to setup all modules required to diagnose a specific class of problems. The DB_Perf profile is the suggest module to use for RDA when troubleshooting performance tuning issues.
OPDG	Oracle Performance Diagnostic Guide is intended to help resolve query tuning, hang/locking, and slow database issues. The guide is not an automated tool but rather seeks to show methodologies, techniques, common causes, and solutions to performance problems.

Hang, Locking and Transient Issues

Some examples are:

· A database that is no longer allowing users to connect.

· A database that is no longer performing work.

· "Select 1 from dual" does not produce output.

· Create table does not complete.

One or more sessions that have completely stopped functioning is usually identified as a locking issue.

Transient issues related to performance are issues that generally occur for a time and then disappear but, during the occurrence, the system is hung or very slow. LTOM and HangFG are tools that assist in collecting the appropriate data when these issues occur.

Use these helpful tools and utilities when troubleshooting hang, locking, and transient issues.

ASH Report (ashrpt.sql)	The ASH report utility is useful for determining the amount of active sessions, what they were doing, and which SQL statements were most active during a period of time. It is especially useful for analyzing transient performance issues. The ashrpt.sql script is found in the $ORACLE_HOME/rdbms/admin directory. NOTE: You must have a license to use this script.
LTOM (Hang Detector, Data Recorder)	The Lite Onboard Monitor (LTOM) is a java program designed as a real-time diagnostic platform for deployment to a customer site. LTOM is proactive rather than reactive and provides real-time automatic problem detection and data collection. LTOM runs on the customer's UNIX server, is tightly integrated with the host operating system and provides an integrated solution for detecting and collecting trace files for system performance issues. Automatic Hang Detection uses a rule based hang detection algorithm. When operating LTOM and this mode is enabled, automatic hang detection proceeds silently in the background while periodically checking for hangs. Once any session has been identified as hung, diagnostic traces are automatically generated. The type of hang diagnostic and number of diagnostic traces collected is determined by what has been defined in the rules file, $TOM_HOME/init/hangDetect.properties. Automatic Data Recording uses a set of rules to determine when to collect data based on monitoring specific wait events. The main advantage of using automatic data recording is that data is collected only when the database is experiencing a performance problem. The rules for this feature are based on database wait events. The automatic data recorder monitors certain V$ views at specified intervals and computes the average wait time between intervals for each event. This computed average wait time is compared to the rule definition for that event, if any. If a rule has been defined for that event and if the average wait time exceeds the rule threshold for that event then LTOM collects data based on an algorithm.
HangFG	HANGFG (Hang file generator) is a series of unix shell scripts used to automate the generation and collection of hanganalyze and systemstate trace files. HANGFG generates and collects hang trace files based on the impact of taking diagnostic traces on a system which is already in a degraded state. The overall decision on what level of impact the user can afford is left up to the user when he runs HANGFG, as the level of impact is passed in as an argument to the tool. HANGFG is also capable of making this decision for the user if the user selects light or medium impact (option 1 or 2) as an argument to the tool. HANGFG is RAC aware and can run in either a RAC or non RAC environment.

Error/Crash Issues

Error/Crash Issues

In this section, error and crash issues refer to ORA-600, ORA-7445 errors, and core dumps. Use the tools below to assist in troubleshooting these types of issues.

Stackx

stackx is a shell script utility for extracting diagnostic stack trace information from core files on UNIX/LINUX platforms. Core files are typically created when an application program fails in such a way it cannot continue operation. Core files contain information on program functions called immediately prior to program failure. This information is called a "stack trace" or "back trace" and is embedded within the binary core file, which is not human readable. In order to extract the useful information and put it into human readable form, some effort is required. stackx assists in that effort. This information can be instrumental in determining the cause of a program failure, if it is extracted properly.

ORA-600/ORA-7445 Troubleshooter

ORA-600 errors are raised from the kernel code of the Oracle RDBMS software when an internal inconsistency is detected or an unexpected condition is met. An ORA-7445 error is raised by an Oracle server process when it has received a fatal signal from the operating system. The ORA-600/ORA-7445 Troubleshooter is a form based tool accessed via MetaLink. The tool provides a description for of the ORA-600 and ORA-7445 errors based on the argument reported with the error. The tool will also perform an advanced MetaLink search to find documents containing relevant sections from the call stack which is generated at the time of the error.

RAC Tuning

Use the RDA tool to obtain helpful performance related data across a RAC cluster.

RDA

Remote Diagnostic Agent (RDA) is a set of command line diagnostic scripts that are executed by an engine written in the Perl programming language. RDA is used to gather detailed information about an Oracle environment; the data gathered is in turn used to aid in problem diagnosis. The output is also useful for seeing the overall system configuration. Oracle Support encourages the use of RDA because it provides a comprehensive picture of the customer's environment. This can greatly reduce service request resolution time by minimizing the number of requests from Oracle Customer Support for more information. RDA is designed to be as unobtrusive as possible; it does not modify systems in any way, it only collects useful data for Oracle Customer Support. Starting from release 4.2, RDA has the capability to perform remote data collections. RDA which is installed on one node can control the installation and execution of RDA on multiple nodes/Oracle homes.

oracle sql query example for comma delimited single row to multiple row separated by comma delimiter

oracle sql query example for comma delimited single row to multiple row separated by comma delimiter
------------------------------------------------------------------------------


SQL> var mylist varchar2(100)
SQL> exec :mylist := '5,11,13,22,23,31,44,45'

PL/SQL procedure successfully completed.

SQL> select substr(:mylist,
2 instr(','||:mylist||',', ',', 1, rn),
3 instr(','||:mylist||',', ',', 1, rn+1)
4 - instr(','||:mylist||',', ',', 1, rn) - 1) value
5 from ( select rownum rn from dual
6 connect by level
7 <= length(:mylist)-length(replace(:mylist,',',''))+1
8 )
9 /
VALUE
-----------------------------------------------------------
5
11
13
22
23
31
44
45

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>