Article 7

March 22, 2016, 10:52 am

≫ Next: Article 6

≪ Previous: Steps for Migrating to ASM using RMAN

Not able to perform any file attachments in apex application

Issue Detail : Users are not able to attach any files in Apex application

Error Type : ORA-00600: internal error code, arguments: [ktspgfb-1].

User Level Problems :

11) Users will not be able to attach any files.

DBA Level Problems :

11) Bounce Apex will not work.

22) Bounce the Database will not work.

ACTION PLAN :

We can perform two action plans for this issue.

a) We have to do expdp/impdp for the table FLOWS_FILES.WWV_FLOW_FILE_OBJECTS$

b) Or we can re-organize the table by moving it to other tablespace and vice versa.

Step by step instruction to re-org the FILES.WWV_FLOW_FILE_OBJECTS$

1a) We have a tablespace FM_BACKUP. So we decided to move the table to this tablespace.

2b) Increase the FM_BACKUP and UNDO_APPSTS1 tablespace with 25 GB more.

3c) Increase undo_retention from 1800 to 14400

Before Moving the table

ALTER USER FLOWS_FILES quota unlimited on FM_BACKUP;

SELECT 'ALTER TABLE '||OWNER|| '.'||TABLE_NAME||' MOVE TABLESPACE FM_BACKUP; ' FROM dba_tables where TABLE_NAME='WWV_FLOW_FILE_OBJECTS$';

ALTER TABLE FLOWS_FILES.WWV_FLOW_FILE_OBJECTS$ MOVE TABLESPACE FM_BACKUP;

select 'alter table '||OWNER|| '.'||table_name||' move '||chr(10)||'LOB ('''||column_name||''') store as '||segment_name||chr(10)||'(tablespace FM_BACKUP);'

from dba_lobs where TABLE_NAME='WWV_FLOW_FILE_OBJECTS$';

alter table FLOWS_FILES.WWV_FLOW_FILE_OBJECTS$ move LOB ("BLOB_CONTENT") store as SYS_LOB0000403125C00017$$ (tablespace FM_BACKUP);

SELECT 'ALTER INDEX ' || OWNER ||'.'||index_name ||' REBUILD tablespace FM_BACKUP ONLINE COMPUTE STATISTICS;' from dba_indexes where table_name='WWV_FLOW_FILE_OBJECTS$';

ALTER INDEX FLOWS_FILES.WWV_FLOW_FILES_USER_IDX REBUILD tablespace FM_BACKUP ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.WWV_FLOW_FILES_FILE_IDX REBUILD tablespace FM_BACKUP ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.SYS_C00205743 REBUILD tablespace FM_BACKUP ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.WWV_FLOW_FILE_OBJ_PK REBUILD tablespace FM_BACKUP ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.SYS_IL0000403125C00017$$ REBUILD tablespace FM_BACKUP ON LINE COMPUTE STATISTICS;

Revert back to original Tablespace;

ALTER TABLE FLOWS_FILES.WWV_FLOW_FILE_OBJECTS$ MOVE TABLESPACE APEX;

alter table FLOWS_FILES.WWV_FLOW_FILE_OBJECTS$ move LOB ("BLOB_CONTENT") store as SYS_LOB0000403125C00017$$ (tablespace APEX);

ALTER INDEX FLOWS_FILES.WWV_FLOW_FILES_USER_IDX REBUILD tablespace APEX ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.WWV_FLOW_FILES_FILE_IDX REBUILD tablespace APEX ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.SYS_C00205743 REBUILD tablespace APEX ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.WWV_FLOW_FILE_OBJ_PK REBUILD tablespace APEX ONLINE COMPUTE STATISTICS;

ALTER INDEX FLOWS_FILES.SYS_IL0000403125C00017$$ REBUILD tablespace APEX ONLINE COMPUTE STATISTICS;

Revert back the undo retention to 1800

Issue Fixed:

---------------

FLOWS_FILES.WWV_FLOW_FILE_OBJECTS$ has been re-organized. Please check doing the attachments now.

↧

Article 6

March 22, 2016, 10:54 am

≫ Next: Article 5

≪ Previous: Article 7

How To Confirm LOB Segment Corruption Using Export Utility

create table corrupted_lob_data (corrupted_rowid rowid);

set concat off

declare
error_1555 exception;
pragma exception_init(error_1555,-1555);
num number;
begin
for cursor_lob in (select rowid r, &&lob_column from &table_owner.&table_with_lob) loop
begin
num := dbms_lob.instr (cursor_lob.&&lob_column, hextoraw ('889911')) ;
exception
when error_1555 then
insert into corrupted_lob_data values (cursor_lob.r);
commit;
end;
end loop;
end;
/

After running the above procedure, it prompts for:

Enter value for lob_column : EMP_XML
Enter value for table_owner : SCOTT
Enter value for table_with_LOB: EMP

Like this, we can check the corruption in all the LOB columns.

In this example, the output of the table “CORRUPTED_LOB_DATA” is showing three rowid’s referencing the corrupted lob segment

select * from corrupted_lob_data;

CORRUPTED_ROWID
---------------------
AAEWBsAAGAAACewAAC
AAEWBsAAGAAACewAAF
AAEWBsAAGAAACewAAG

3 rows selected
Confirm the LOB corruption using Datapump:

#> expdp scott/tiger directory=data_pump_dir dumpfile=test.dmp logfile=test.log tables=EMP query=\"where rowid = \'AAEWBsAAGAAACewAAC\'\"

#> expdp scott/tiger directory=data_pump_dir dumpfile=test1.dmp logfile=test1.log tables=EMP query=\"where rowid = \'AAEWBsAAGAAACewAAF\'\"

#> expdp scott/tiger directory=data_pump_dir dumpfile=test2.dmp logfile=test2.log tables=EMP query=\"where rowid = \'AAEWBsAAGAAACewAAG \'\"
Or, confirm the LOB corruption using original export:

#> exp scott/tiger file=test.dmp log=test.log tables=EMP query=\"where rowid = \'AAEWBsAAGAAACewAAC\'\"

#> exp scott/tiger file=test1.dmp log=test1.log tables=EMP query=\"where rowid = \'AAEWBsAAGAAACewAAF\'\"

#> exp scott/tiger file=test2.dmp log=test2.log tables=EMP query=\"where rowid = \'AAEWBsAAGAAACewAAG\'\"
If any of the above export fails then the LOB corruption confirmed.

SOLUTION

1) Restore and recover the LOB segment using physical backup.

- OR -

2) Empty the affected LOBs using the UPDATE statement as mentioned in the Note 787004.1:

-- NOTE: for BLOB and BFILE columns use EMPTY_BLOB; for CLOB and NCLOB columns use EMPTY_CLOB, e.g.:

update EMP
set EMP_XML = empty_blob()
where rowid in (select corrupted_rowid
from corrupted_lob_data);
commit;

3) Perform the export excluding the corrupted rowids.

Using DataPump export:
----------------------
#> expdp scott/tiger directory=data_pump_dir dumpfile=test.dmp logfile=test.log tables=EMP query=\"where rowid not in $\'AAEWBsAAGAAACewAAC\', \'AAEWBsAAGAAACewAAF\', \'AAEWBsAAGAAACewAAG\'$\"

Using original export:
----------------------
#> exp scott/tiger file=test.dmp log=test.log tables=EMP query=\"where rowid not in $\'AAEWBsAAGAAACewAAC\', \'AAEWBsAAGAAACewAAF\', \'AAEWBsAAGAAACewAAG\'$\"

- OR -

4) Alternatively, you could use flashback query to solve the LOB corruption. However, details are beyond the scope of this article.

For more information, please refer to http://docs.oracle.com/cd/B28359_01/appdev.111/b28424/adfns_flashback.htm#i1008579

↧

Article 5

March 22, 2016, 11:06 am

≫ Next: Article 4

≪ Previous: Article 6

Facing XDB Authentication message, while accessing Apex application

There may be several different cause for this issue. But in our case, the below steps fixed the issue.

1) Download apex_verify.sql from metalink and that script will generate an html file. Open it and check for the below information.

a) ANONYMOUS account status and all the apex related user account status. If any users are LOCKED, please UNLOCK it.
b) INVALIDS of apex objects. If found, compile it by executing utlrp.sql
c) If not able to guess the problem, upload it to oracle SR.

2) In our case, we found that the apex was using a non-default image prefix after database restoration. This is not possible or not allowed and it must be /i/, if we are using EPG.

3) Hence, we should run the reset_image_prefix.sql script in our $ORACLE_HOME/apex/utilities and reset the images alias back to /i/.

4) If our database is upgraded we must run the apex_epg_config.sql (This point is only applicable, if we have upgraded our database).

↧

Article 4

March 22, 2016, 11:31 am

≫ Next: Article 3

≪ Previous: Article 5

Configuring Customized Theme in Apex Application

Incident Detail: After cloning the datbase through RMAN utility. The apex application customized theme does’nt worked. But the workspace images are configured.

Root Cause:

1) When a database clone is made of an EPG Apex DB instance via 'EMGC RMAN active database cloning', the DISPATCHERS information does NOT come across in the clone, and DISPATCHERS has to be fixed manually.

2) Theme needs to be configured manually after cloning.

High Level Steps For Fixing this issue:

1) Define an entry in the init.ora (<sid> must be replaced by the sid of your version 11 db): dispatchers="(PROTOCOL=TCP)(SERVICE=<sid>XDB)".

In our case SERVICE=ORCLXDB

2) Bounce the database(Start with pfile).

3) Unzip the them-smart-admin(theme) and this folder needs to be uploaded to the apex/images/themeslocation through File Transfer Protocol(FTP) – (Filezilla is the best option).

Note : Just drag and drop option will not work.

4) Reload the images again using the apex reload script.

5) Disable the HTTP port.

6) Bounce the database once.

7) Enable the HTTP port in 8080.

↧

Article 3

March 22, 2016, 11:44 am

≫ Next: Article 2

≪ Previous: Article 4

Steps to Purge the OPTSTATs:

1) Show the current history level:

select dbms_stats.get_stats_history_availability from dual;

2) Assuming history is 100 days old and you want to purge it until 10 days old:

begin

for i in reverse 10..100

loop

dbms_stats.purge_stats(sysdate-i);

end loop;

end;

3) Show the new history level

select dbms_stats.get_stats_history_availability from dual;

4) Output must show that the GET_STATS_HISTORY_AVAILABILITY is equal to sysdate - (n).

↧

Article 2

March 22, 2016, 11:57 am

≫ Next: TO CHANGE THE SNAPSHOT SETTINGS

≪ Previous: Article 3

Query to check the Average ran time of a Concurrent Request from FND history backup table.

select DESCRIPTION, request_id, request_date, phase_code, status_code, requested_start_date,
actual_start_date, actual_completion_date,ROUND(((nvl(actual_completion_date,sysdate) -actual_start_date) * 1440)/60,2) "Runtime (in hours)" ,
argument_text from apps.fnd_conc_req_history
where
DESCRIPTION in ('&program_name')
and actual_start_date between to_date('21-04-2015 00:00:00','DD-MM-YYYY HH24:MI:SS')
and to_date('22-04-2015 23:59:59','DD-MM-YYYY HH24:MI:SS')
order by request_date desc

The above script will show the average running time of a particular request using backup table. If backup table for FND concurrent requests are available, Please edit it using your table name.

↧

TO CHANGE THE SNAPSHOT SETTINGS

March 22, 2016, 2:25 pm

≫ Next: How to restore default system permissions on Red Hat, CentOs, Fedora

≪ Previous: Article 2

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

SELECT retention FROM dba_hist_wr_control;

RETENTION
---------------------------------------------------------------------------
+00008 00:00:00.0

1 row selected.

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

SQL>

The retention period is altered using the MODIFY_SNAPSHOT_SETTINGS procedure, which accepts a RETENTION parameter in minutes.

BEGIN
DBMS_WORKLOAD_REPOSITORY.modify_snapshot_settings(
retention => 43200); -- Minutes (= 30 Days).
END;
/

SELECT retention FROM dba_hist_wr_control;

↧

How to restore default system permissions on Red Hat, CentOs, Fedora

March 22, 2016, 9:51 pm

≫ Next: Article 3

≪ Previous: TO CHANGE THE SNAPSHOT SETTINGS

I recently changed the file permission of root (/) directories to 777(recursively).
While I start my OS it does not shows any login screen.

The rpm has a parameter called --setperms and --setugids. Using this we can recover our Operating System

Boot/reboot machine
At blue RedHat screen press any key to enter the boot loader
Press 'e' to edit the most recent boot command
Use the arrow keys to select the line that starts with "kernel"
Press 'e' to edit the kernel command
Append 'S' to the end of the line. There should be a space before the previous end of the line (probably 'quiet') and the 'S'. Capitalization matters.
Hit Enter to commit the change
Hit 'b' to boot

Enter this in the root prompt.

 1) To reset uids and gids on files and directories

for u in $(rpm -qa); do rpm --setugids $u; done



2) To permissions on files and directories

for p in $(rpm -qa); do rpm --setperms $p; done






Done!!

↧

Article 3

March 23, 2016, 12:18 am

≫ Next: Article 2

≪ Previous: How to restore default system permissions on Red Hat, CentOs, Fedora

ORA-15018, ORA-15099 When Creating Diskgroup in ASM

When i am trying to create your first diskgroup on the ASM instance in rac setup. However, it fails when the disk size is above 2 Terabyte in size. And found out that Since you have already installed patch 6453944, you are receiving the error ORA-15099.

As a result of the fix, ORA-15099 will be raised if LUN/disk is larger than 2TB size.

You may also experience INS-20802 if running ASMCA from the installation process.

SOLUTION:

If the disk size is greater than 2TB, please resize the LUN/disk to a size under 2 Terabytes. Then you will be able to create the diskgroup.

It's ok to use disks with exactly 2TB size.

Note: Even with fix of 6453944 , 2TB is still the limit on 11.2 version on nonExadata set up.

So it is better to have LUN/disk under 2 TB , This is applicable to all linux platforms.

Ref Doc ID 1057333.1

↧

Article 2

March 23, 2016, 12:55 am

≫ Next: Article 1

≪ Previous: Article 3

Enabling Automated SQL Tuning in Oracle 11g

You need to identify if Automatic SQL Tuning job is enabled and regularly running. Use the following query to determine if any Automatic SQL Tuning jobs are enabled:

Use the following query:

SELECT client_name, status, consumer_group, window_group FROM dba_autotask_client ORDER BY client_name;

To enable the sql tuning advisor sue the following procedure

----------------------------------------------------------------------------

BEGIN

DBMS_AUTO_TASK_ADMIN.ENABLE(

client_name => 'sql tuning advisor',

operation => NULL,

window_name => NULL);

END;

And check now with the same query to cross check.

SELECT client_name, status, consumer_group, window_group FROM dba_autotask_client ORDER BY client_name;

↧

Article 1

March 23, 2016, 8:59 am

≫ Next: Article 0

≪ Previous: Article 2

SQLLoader-128: unable to begin a session ORA-01017: invalid username/password; logon denied

Error:
Programs were erroring out with below error.
Arguments
------------
/u01/prod/attach/1418160319478.txt
------------
ORA-01017: invalid username/password; logon denied
SQLLoader-704: Internal error: ulconnect: OCISessionBegin [-1]

SQLLoader: Release 8.0.6.3.0 - Production on Tue Dec 9 22:59:13 2014

(c) Copyright 1999 Oracle Corporation. All rights reserved.

ORA-01017: invalid username/password; logon denied
SQLLoader-704: Internal error: ulconnect: OCISessionBegin [-1]

Program exited with status 1
Concurrent Manager encountered an error while running SQL*Loader for your concurrent request 140568679.

Review your concurrent request log file for more detailed information.

+---------------------------------------------------------------------------+
Executing request completion options...

Sol:
When we started trouble shooting we found below points.

- Parameter processes it has been changed from 1528 to 2000 in the init.ora file
- FNDSM log file is below the 2GB.
- The program hasn't been scheduled by an ended user ( Bug 12896168 )
- Instance is using it's own service name (Doc ID 1160553.1)
- Program executable permissions have been check
- Issue occurs in RAC and non RAC environments

For our issue it was caused by the size of the FNDSM log which was over 2GB.
-rw-r--r-- 1 appp14 oaa 2147483647 Dec 9 21:15 FNDSM257792.mgr

To fix the issue, we have truncated the file.
> FNDSM257792.mgr

After that user ran the program and it got completed successfully.

↧

Article 0

March 23, 2016, 9:01 am

≫ Next: Script to list recursive dependency between objects

≪ Previous: Article 1

Query to trace file location for the concurrent program

SELECT 'Request id: '||request_id ,

'Trace id: '||oracle_Process_id,

'Trace Flag: '||req.enable_trace,

'Trace Name:

'||dest.value||'/'||lower(dbnm.value)||'_ora_'||oracle_process_id||'.trc',

'Prog. Name: '||prog.user_concurrent_program_name,

'File Name: '||execname.execution_file_name|| execname.subroutine_name ,

'Status : '||decode(phase_code,'R','Running')

||'-'||decode(status_code,'R','Normal'),

'SID Serial: '||ses.sid||','|| ses.serial#,

'Module : '||ses.module

from fnd_concurrent_requests req, v$session ses, v$process proc,

v$parameter dest, v$parameter dbnm, fnd_concurrent_programs_vl prog,

fnd_executables execname

where req.request_id = &request

and req.oracle_process_id=proc.spid(+)

and proc.addr = ses.paddr(+)

and dest.name='user_dump_dest'

and dbnm.name='db_name'

and req.concurrent_program_id = prog.concurrent_program_id

and req.program_application_id = prog.application_id

and prog.application_id = execname.application_id

and prog.executable_id=execname.executable_id;

↧

Script to list recursive dependency between objects

March 24, 2016, 3:47 am

≫ Next: Install Oracle Flow Builder

≪ Previous: Article 0

Rem
Rem NAME
Rem rdeptree.sql - Show objects which a given object is recursively
Rem dependent on
Rem DESCRIPTION
Rem This procedure, view and temp table will allow you to see all
Rem objects that a given object recursively depends on.
Rem Note: you will only see objects for which you have permission.
Rem Examples:
Rem execute rdeptree_fill('procedure', 'scott', 'billing');
Rem select * from rdeptree order by seq#;
Rem
Rem execute rdeptree_fill('table', 'scott', 'emp');
Rem select * from rdeptree order by seq#;
Rem
Rem execute rdeptree_fill('package body', 'scott', 'accts_payable');
Rem select * from rdeptree order by seq#;
Rem
Rem A better way to display this information than:
Remselect * from rdeptree order by seq#;
Rem is
Rem select * from irdeptree;
Rem
Rem This shows the dependency relationship via indenting. Notice
Rem that no order by clause is needed with ideptree.
Rem RETURNS
Rem
Rem NOTES
Rem Run this script once for each schema that needs this utility.

drop sequence rdeptree_seq
/
create sequence rdeptree_seq cache 200 /* cache 200 to make sequence faster */
/
drop table rdeptree_temptab
/
create table rdeptree_temptab
(
object_id number,
referenced_object_id number,
nest_level number,
seq# number
)
/
create or replace procedure rdeptree_fill (type char, schema char, name char) is
obj_id number;
begin
delete from rdeptree_temptab;
commit;
select object_id into obj_id from all_objects
where owner = upper(rdeptree_fill.schema)
and object_name = upper(rdeptree_fill.name)
and object_type = upper(rdeptree_fill.type);
insert into rdeptree_temptab
values(0, obj_id, 0, 0);
insert into rdeptree_temptab
select object_id, referenced_object_id,
level, rdeptree_seq.nextval
from public_dependency
connect by object_id = prior referenced_object_id
start with object_id = rdeptree_fill.obj_id;
exception
when no_data_found then
raise_application_error(-20000, 'ORU-10013: ' ||
type || '' || schema || '.' || name || ' was not found.');
end;
/

drop view rdeptree
/

set echo on

set echo off
create view rdeptree
(nested_level, type, schema, name, seq#)
as
select d.nest_level, o.object_type, o.owner, o.object_name, d.seq#
from rdeptree_temptab d, all_objects o
where d.referenced_object_id = o.object_id (+)
/

drop view irdeptree
/
create view irdeptree (dependencies)
as
select lpad('',3*(max(nested_level))) || max(nvl(type, '')
|| '' || schema || decode(type, NULL, '', '.') || name)
from rdeptree
group by seq# /* So user can omit sort-by when selecting from ideptree */
/

↧

Install Oracle Flow Builder

March 24, 2016, 5:39 am

≫ Next: RMAN Duplicate database – If DD Boost is the Media Manager Library.

≪ Previous: Script to list recursive dependency between objects

↧

RMAN Duplicate database – If DD Boost is the Media Manager Library.

March 24, 2016, 5:47 am

≫ Next: Shutdown options in a oracle database

≪ Previous: Install Oracle Flow Builder

↧

Shutdown options in a oracle database

March 24, 2016, 6:04 am

≫ Next: Script to Analyze Library cache timeout.

≪ Previous: RMAN Duplicate database – If DD Boost is the Media Manager Library.

Please find the below shutdown options

PS CU TC SC NU

Shutdown abort N N N N N

Shutdown immediate Y Y N N N

Shutdown transactional Y Y Y N N

Shutdown normal Y Y Y Y N

PS -- PROPER SHUTDOWN

CU -- CHECKPOINT UPDATE

TC -- TRANSACTION COMPLETE

SC -- SESSION CLOSED

NU -- NEW USER

Shutdown abort : (Instance Failure)
---------------------

--- Nothing will happen among the above.

Shutdown immediate
----------------------------

Only do PS and CU. Not allow TC,SC,NU

Shutdown transactional
-----------------------------

Only do PS,CU and TC (Only Current transaction will get complete which is happening in the db)

Not allow SC,NU

Shutdown normal
-----------------------

All the above will happen except NU (will not allow).

In Realtime we are using shutdown immediate where Proper shutdown and Checkpoint will update(ie SCN)

↧

Script to Analyze Library cache timeout.

March 24, 2016, 6:17 am

≫ Next: Rotating Listener Logs without Bouncing the Listener

≪ Previous: Shutdown options in a oracle database

ORA-04021 timeout occurred while waiting to lock object %s%s%s%s%s.
Cause: While trying to lock a library object, a time-out occurred.
Action: Retry the operation later.

To find Blocking Session and Waiting Session, use the following sql.

select /*+ ordered */ w1.sid waiting_session,
h1.sid holding_session,
w.kgllktype lock_or_pin,
w.kgllkhdl address,
decode(h.kgllkmod, 0, 'None', 1, 'Null', 2, 'Share', 3, 'Exclusive',
'Unknown') mode_held,
decode(w.kgllkreq, 0, 'None', 1, 'Null', 2, 'Share', 3, 'Exclusive',
'Unknown') mode_requested
from dba_kgllock w, dba_kgllock h, v$session w1, v$session h1
where
(((h.kgllkmod != 0) and (h.kgllkmod != 1)
and ((h.kgllkreq = 0) or (h.kgllkreq = 1)))
and
(((w.kgllkmod = 0) or (w.kgllkmod= 1))
and ((w.kgllkreq != 0) and (w.kgllkreq != 1))))
and w.kgllktype = h.kgllktype
and w.kgllkhdl = h.kgllkhdl
and w.kgllkuse = w1.saddr
and h.kgllkuse = h1.saddr
/

↧

Rotating Listener Logs without Bouncing the Listener

March 24, 2016, 6:19 am

≫ Next: Article 5

≪ Previous: Script to Analyze Library cache timeout.

Please find the below steps to rotate a listener logs.

The first parameter is simply the database SID represented as $1 and the second parameter is full path of the current listener log.

# rotate_listener_log.sh
. ~/env/${1}_ORACLE
LOGFILE=${2}
DATE_STAMP=`date +%m%d%y%s`

lsnrctl <<END
set current_listener ${1}
set log_status off
exit
END
mv $LOGFILE $LOGFILE.${DATE_STAMP}
lsnrctl <<END
set current_listener ${1}
set log_status on
exit
END
zip $LOGFILE.${DATE_STAMP}.zip $LOGFILE.${DATE_STAMP}
rm $LOGFILE.${DATE_STAMP}

Please use the below script in action.

$ ls -ltr $LISTENER_LOG_HOME
total 41316
-rw-rw-r-- 1 oradevl dba     2663 Jun 10 10:23 dev.log.0610111307715830.zip
-rw-rw---- 1 oradevl dba      888 Jun 10 10:23 dev.log
$ ./rotate_listener_log.sh DEV /u01/appdevl/oracle/devdb/11.1.0/log/diag/tnslsnr/myhost
/dev/trace/dev.log

LSNRCTL for Linux: Version 11.1.0.7.0 - Production on 10-JUN-2011 10:24:59

Copyright (c) 1991, 2008, Oracle.  All rights reserved.

Welcome to LSNRCTL, type "help" for information.

LSNRCTL> Current Listener is DEV
LSNRCTL> Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROCDEV))
DEV parameter "log_status" set to OFF
The command completed successfully
LSNRCTL>
LSNRCTL for Linux: Version 11.1.0.7.0 - Production on 10-JUN-2011 10:24:59

Copyright (c) 1991, 2008, Oracle.  All rights reserved.

Welcome to LSNRCTL, type "help" for information.

LSNRCTL> Current Listener is DEV
LSNRCTL> Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROCDEV))
DEV parameter "log_status" set to ON
The command completed successfully
LSNRCTL>   adding: u01/appdevl/oracle/devdb/11.1.0/log/diag/tnslsnr/myhost/dev
/trace/dev.log.0610111307715899 (deflated 80%)
$ ls -ltr $LISTENER_LOG_HOME
total 41320
-rw-rw-r-- 1 oradevl dba     2663 Jun 10 10:23 dev.log.0610111307715830.zip
-rw-rw-r-- 1 oradevl dba      579 Jun 10 10:24 dev.log.0610111307715899.zip
-rw-rw---- 1 oradevl dba      931 Jun 10 10:25 dev.log


Please put it in ur cron once everything is set.
crontab -l
# cleanup listener logs
15 3 1 * * /usr/bin/find /u01/appdevl/oracle/devdb/11.1.0/log/diag/tnslsnr/myhost/dev/trace  -mtime +365 -exec rm -rf {} \;
# rotate listener logs
0 0 1 * * /scratch/oracle/dba/scripts/rotate_listener_log.sh DEV /u01/appdevl/oracle/devdb/11.1.0/log/diag/tnslsnr/myhost/dev/trace/dev.log

↧

Article 5

March 25, 2016, 11:34 am

≫ Next: Article 4

≪ Previous: Rotating Listener Logs without Bouncing the Listener

Log files related to cloning in R12.1.3

Preclone log files in source instance:

Database Tier –
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)

Application Tier –
$INST_TOP/apps/$CONTEXT_NAME/admin/log/(StageAppsTier_MMDDHHMM.log)

Clone log files in target instance:

Database Tier –
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log

Apps Tier –
$INST_TOP/admin/log/ApplyAppsTier_.log

↧

Article 4

March 25, 2016, 11:38 am

≫ Next: Article 3

≪ Previous: Article 5

R12.1.3 Installation Logs

Database Tier Installation
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTechStack_.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ohclone.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/make_.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/installdbf.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adcrdb_.log RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDatabase_.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME//adconfig.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME//NetServiceHandler.log

Application Tier Installation
$INST_TOP/logs/.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppsTechStack.log
$INST_TOP/logs/ora/10.1.2/install/make_.log
$INST_TOP/logs/ora/10.1.3/install/make_.log
$INST_TOP/admin/log/ApplyAppsTechStack.log
$INST_TOP/admin/log/ohclone.log
$APPL_TOP/admin/$CONTEXT_NAME/log/installAppl.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppltop_.log
$APPL_TOP/admin/$CONTEXT_NAME/log//adconfig.log
$APPL_TOP/admin/$CONTEXT_NAME/log//NetServiceHandler.log

Inventory Registration:
$Global Inventory/logs/cloneActions.log
$Global Inventory/logs/oraInstall.log
$Global Inventory/logs/silentInstall.log

↧