Tuesday, 17 October 2017

ORA-32004

Facing below issue on Oracle 12c database.

SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance 
ORACLE instance started.

solution:-

Down Database.
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

Edit PFILE:-

Go to PFILE location.
[sujeet@oracle ~]$ cd $ORACLE_HOME/dbs


[sujeet@oracle dbs]$ vi initORCL.ora

commit below parameter.
#sec_case_sensitive_logon = FALSE

save pfile.

start database with pfile.

SQL> startup pfile=/apps/dba/db/tech_st/12.1.0.2/dbs/initORCL.ora
ORACLE instance started.

Total System Global Area 2147483648 bytes
Fixed Size                  2926472 bytes
Variable Size             872417400 bytes
Database Buffers         1258291200 bytes
Redo Buffers               13848576 bytes
Database mounted.
Database opened.

SQL> create spfile from pfile;

File created.


SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down


SQL> startup
ORACLE instance started.

Total System Global Area 2147483648 bytes
Fixed Size                  2926472 bytes
Variable Size             872417400 bytes
Database Buffers         1258291200 bytes
Redo Buffers               13848576 bytes
Database mounted.
Database opened.

Issue resolved.


Thursday, 12 October 2017

Upgrade Timezone version 10 to 18 in oracle

Upgrading timezone_file version manually during Oracle 12c upgrade

Some of us might have faced a situation to upgrade timezone_file version manually during Oracle 12c upgrade. Here are the steps to follow in Windows.

When you upgrade Oracle to 121020, you will have have an option in DBUA to upgrade the timezone data.





If you don’t check it, then, when you run “post_upgrade_checks.sql”, it will give you the below warning message.

**********************************************************************
Check Tag:     OLD_TIME_ZONES_EXIST
Check Summary: Check for use of older timezone data file
Fix Summary:   Update the timezone using the DBMS_DST package after upgrade is complete.
**********************************************************************
Fixup Returned Information:
INFORMATION: --> Older Timezone in use
     Database is using a time zone file older than version 18.
     After the upgrade, it is recommended that DBMS_DST package
     be used to upgrade the 12.1.0.2.0 database time zone version
     to the latest version which comes with the new release.
     Please refer to My Oracle Support note number 977512.1 for details.

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

upgrade it manually

Upgrade Time zone version 10 to 18.

SQL> SELECT version FROM v$timezone_file;
  
  VERSION
----------
        10

SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;

PROPERTY_NAME                                                             VALUE
------------------------------------------------------------------ ------------------------------
DST_PRIMARY_TT_VERSION                                             10
DST_SECONDARY_TT_VERSION                                        0
DST_UPGRADE_STATE                                                       NONE

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup upgrade
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size                  2926472 bytes
Variable Size             889194616 bytes
Database Buffers         1241513984 bytes
Redo Buffers               13848576 bytes
Database mounted.
Database opened.

SQL> EXEC DBMS_DST.BEGIN_UPGRADE (18);

PL/SQL procedure successfully completed.

SQL> shut immediate

SQL> startup

SQL> SELECT version FROM v$timezone_file;

   VERSION
----------
        18


Wednesday, 20 September 2017

Enable Trace for Concurrent Programs in Oracle Apps R12.1.3

Tracing the Concurrent program is very good option to Debug any issue while running the concurrent program.


Agenda :

 To enable the Trace for Concurrent Programs
 To Debug the issues in Concurrent Programs or its dependent objects.

Steps :

 1. Goto Concurrent Program Definition

Application Developer –> Concurrent –> Program –> check Enable Trace

save it.

Query your concurrent program and check the Enable Trace check box at the bottom of the screen.

2. Set the Profile Concurrent: Allow Debugging to YES.

save it.

3. Navigate to the Responsibility from where you are running the program.

4. Before Submitting the Concurrent Program in Submit Request screen there will be an option like Debug Options click on that button.

5. In the Debug Options select the SQL Trace and enable Trace with binds.

6. Submit the Concurrent Program and note down the Request id.

7.Trace file name will always be post fixed with oracle_process_id.To get the oracle_process_id use the below SQL
 select oracle_process_id from fnd_concurrent_requests where request_id= Request_id;

8.And the Trace file path can be derived using the below

SQL> Select * from v$parameter where name=’user_dump_dest’;

Trace file location:-
/apps/sonu/db/tech_st/11.1.0/admin/SONU_oracle/diag/rdbms/sonu/SONU/trace

How ro convert .trc to .out file :-
tkprof ACSDEV_ora_15529_SEKARS.trc ACSDEV_ora_15529_SEKARS.out  explain=apps/apps  sys=no sort=PRSDSK,EXEDSK,FCHDSK,EXECPU,FCHCPU


9. Get the trace file to your local machine.Understanding the raw trace is very complex so use
TKPROF utility to make the Trace file readable.

10. Open the Command Prompt and run the below command
 TKPROF < Trace File_Name.trc> <Output_File_Name.out> SORT=fchela

11.A new outfile will be generated with the name given in the above command.
Analyse the Output file to know the answers for your problem.


Sql queries to find the log files by Request id


select req.oracle_process_id tracename, req.request_id, req.requested_by,usr.user_name,
prog.user_concurrent_program_name, req.request_date, req.phase_code, req.status_code, req.logfile_name ,
req.outfile_name, dest.value as user_dump_dest from apps. fnd_concurrent_requests req, gv$parameter dest,
apps.fnd_concurrent_programs_vl prog, apps.fnd_user usr

where  req. concurrent_program_id = prog.concurrent_program_id

and req.requested_by = usr.user_id

–and request_id like '17352717'

and dest.name= 'user_dump_dest'

and request_id like & Request_id;


Sql query find the log files by username


select req.oracle_process_id tracename, req.request_id, req.requested_by,usr.user_name,
prog.user_concurrent_program_name, req.request_date,  req.phase_code, req.status_code, req.logfile_name ,
req.outfile_name, dest.value as user_dump_dest

from apps. fnd_concurrent_requests req, gv$parameter dest, apps.fnd_concurrent_programs_vl prog, apps.fnd_user usr

where  req. concurrent_program_id = prog.concurrent_program_id

and req.requested_by = usr.user_id

–and request_id like '17352717'

and dest.name= ‘user_dump_dest’

and usr.user_name like ‘sujeet%jha%’

order by request_date desc



SQL> select oracle_process_id from fnd_concurrent_requests where request_id = &Request_id;

 SQL> select * from apps. fnd_concurrent_requests req,gv$parameter dest , apps .fnd_concurrent_programs_vl prog
where  req. concurrent_program_id = prog.concurrent_program_id and request_id like '17352717' and dest.name= ‘user_dump_dest’

Tuesday, 5 September 2017

How to add employee detail in oracle apps R12

Employee creation and user mapping
Employee creation, Employee role assignments and user mapping:

Issue reason:
       
Some times we are getting permission issue while accessing some of the module/responsibility like
 'iReceivable, Service, Credit management Credit analyst' etc. For that we have to create new employee,import that employee,
 and assign roles (Not mandatory) finally map that employee into Application login user "Person field".

Creating an employee
An employee is the most important entity in an organization. Before creating an employee, the HR officer must know the date from which the employee will be active in the organization. In Oracle terminology, you can call it the employee's hire date. Apart from this, the HR officer must know basic details of the employee such as first name, last name, date of birth, and so on.

Navigation: Global HRMS Manager -->People -->Enter and Maintain.





Select new and enter employee details like name,gender from action tab select "Create Employment
" option for employee creation. And enter identification employee number and save it , then enter the address details.





 Import the Employee:

CRM Administrator --> Resource Manager -->import Resource

From report category page enter your employee name and search employee.
 After finding employee select the employee and click start import button. and click ok Finally select save resource button.

You want to assign any role for this employee means click details button and assign the required roles.
(Credit analyst, credit manager, collection agent, collection manager etc..)

Employee Mapping:

If employee creation process is done, map this employee with application user.
Navigation:  System administrator -->Security --> user --> Define

Query the application user and select this employee in person field, and save it.  

Friday, 1 September 2017

ORA-32006

ORA-32006: SEC_CASE_SENSITIVE_LOGON initialization parameter has been deprecated
ORA-32006: PARALLEL_AUTOMATIC_TUNING Initialization Parameter Has Been Deprecated

SQL> startup 
ORA-32004: obsolete and/or deprecated parameter(s) specified 
ORACLE instance started. 

Total System Global Area 167772160 bytes 
Fixed Size 1247900 bytes 
Variable Size 75498852 bytes 
Database Buffers 88080384 bytes 
Redo Buffers 2945024 bytes 
Database mounted. 
Database opened. 

SYMPTOMS

After setting the database initialization parameter: parallel_automatic_tuning='TRUE' in the initialization file: <init>.ora, the database startup returns:

ORA-32006: PARALLEL_AUTOMATIC_TUNING initialization parameter has been deprecated
The database starts as per normal.
The parameter is set as required by the OWB installation documentation.

CAUSE

The PARALLEL_AUTOMATIC_TUNING parameter has caused the error.

This parameter is no longer required. Refer to:
Warehouse Builder 10g Release 1 Installation Addendum section 1.3.2 PARALLEL_AUTOMATIC_TUNING Parameter:

"Section A.2 (page A-3) instructs you to set the PARALLEL_AUTOMATIC_TUNING parameter to TRUE. This parameter is deprecated in Oracle Database 10g.
Do not set the PARALLEL_AUTOMATIC_TUNING parameter in Oracle Database 10g."

SOLUTION

The parameter should not be set and can be removed from the database initialization file(PFILE).
Start database with Pfile.
Create spfile from Pfile.

Note:-

Security parameters in 11G and 12C

There are 5 parameters that are all prefixed with ‘sec’ in an 11g and 12c database.
Actually that is a lie because one is now deprecated in 12c. They are all, as you might guess related to security.

SEC_CASE_SENSITIVE_LOGON                                 TRUE in 11GR1 , 11GR2, DEPRECATED IN 12C
SEC_MAX_FAILED_LOGIN_ATTEMPTS                 default 11GR1,11GR2=10, 12c=3
SEC_PROTOCOL_ERROR_FURTHER_ACTION default is  CONTINUE in 11GR1, 11GR2, drop, 3 in 12c
SEC_PROTOCOL_ERROR_TRACE_ACTION        default is TRACE 11GR1,11GR2, 12c
SEC_RETURN_SERVER_RELEASE_BANNER           default is FALSE in 11GR1, 11GR2, TRUE in 12c

Thursday, 31 August 2017

ORA-09925


ORA-09925: Unable to create audit trail file

I was received this error message when I was started my database.

[oracle@sonu ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Thu Aug 31 09:22:44 2017

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

ERROR:
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 30: Read-only file system
Additional information: 9925
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 30: Read-only file system
Additional information: 9925

CAUSE

The filesystem inodes are exhausted.

Solution:-

 I rebooted my machine and got following messages which pointed to some
errors encountered during filesystem check and instructed to run fsck manually.

[root@sonu ~]# init 6

Checking filesystems

/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
*** An error occurred during the filesystem check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance (or type Control-D to continue):

– I entered password for root to initiate filesystem check.
As a result I was prompted multiple no. of times to allow fixing of  various filesystem errors.

(Repair filesystem) 1 # fsck
Fix(y)?
- After all the errors had been fixed, filesystem check was restarted

Restarting e2fsck from the beginning...

/: ***** FILE SYSTEM WAS MODIFIED *****
/: ***** REBOOT LINUX *****
- After filesystem had been finally checked to be correct, I exited for reboot to continue.

(Repair filesystem) 2 # exit

– After the reboot, I could successfully connect to my database as sysdba .

[oracle@sonu ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Sat Jul 12 09:21:52 2014

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

Connected to an idle instance.

[oracle@sonu ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Thu Aug 31 10:24:43 2017

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

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size                  2932632 bytes
Variable Size             549453928 bytes
Database Buffers          515899392 bytes
Redo Buffers                5455872 bytes
Database mounted.
Database opened.

SQL> select name from v$database;

NAME
---------
sujeet

Issue resolved.

Wednesday, 23 August 2017

Agent and Host Targets not Shown in OEM


EM 12c, EM 13c : Agent and Host Targets not Shown in the Enterprise Manager Cloud Control Targets List after Agent Installation (Doc ID 1934665.1)


GOAL

Agent and Host targets are not shown in the EM 12c console after a successful Agent installation.
 This note describes how to manually add them.

SOLUTION

1) Run the following command to verify that the Agent is running and can upload to the OMS:

cd <AGENT_HOME>/bin
emctl status agent
emctl upload

2) Run the following command to verify the Host and Agent targets have been registered on the Agent:

cd <AGENT_HOME>/bin
emctl config agent listtargets

3) If the output from the above command shows no targets, run the following query on the repository database to confirm that the targets are present in the repository.

select ENTITY_NAME, ENTITY_TYPE, MANAGE_STATUS, PROMOTE_STATUS from EM_MANAGEABLE_ENTITIES where emd_url like '%<Agent Host>%';

4) If the output from the above query returns no rows, run the following command from the the Agent host to add the targets registered with the Agent:

cd <AGENT_HOME>/bin
emctl config agent addInternaltargets

Review the All Targets, Host targets or Agent targets lists for new target inclusion.