Sujeet APPS DBA

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

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.

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.

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2

CAUSE

DBA_TEMP_FREE_SPACE for tablespace_name = 'TEMP2' shows:

TABLESPACE_NAME TABLESPACE_SIZE ALLOCATED_SPACE FREE_SPACE
TEMP2 32212254720 1441792 32210812928

--although free space exists, still the temp segment cannot be extended

There is only one file (which is having .tmp extension) existing for the tablespace:

FILE_NAME used MB Max MB AUTOEXTENSIBLE
/u01/data/UAT/datafile/o1_mf_temp2_c519yq1q_.tmp 30720 0 NO

If the database version is higher than 9i , then should have tablespace datafiles as .dbf, not as .tmp So a new .dbf datafile needs to be added for the tablespace.

SOLUTION

Add a new datafile for the tablespace either from command line:

ALTER TABLESPACE TEMP2 ADD TEMPFILE '/u01/data/UAT/datafile/temp02.dbf' SIZE 2000M;

Or by using Enterprise Manager Console.

How to add database in OEM 13c

Navigate to the "Add Targets Manually" screen using the menu at the top-right of the screen

(Setup > Add Target > Add Targets Manually).

Click the "Install Agent on Host" button.

Click the "+ Add" button.

Enter the host and platform, then click the "Next" button.

Create directory on database server

[root@sujeet dba]# mkdir OEM13C_AGENT

[root@sujeet dba]# chown oradba:dba OEM13C_AGENT

[root@sujeet dba]# chmod 777 OEM13C_AGENT

[root@sujeet dba]# pwd

/apps/ebsdba

click on

Named Credential plus link
Enter Database OS user name & password.
click on OK.

click on NEXT

Click on DEPLOY AGENT TAB

When Agent install successfully than

Navigate to the "Add Targets Manually" screen using the menu at the top-right of the screen

(Setup > Add Target > Add Targets Manually).

Click on ADD TARGET DECLARATIVELY

Enter Host name and click on add tab.

Enter Target name:- SID NAME.

Database system:- Database OS USER NAME.

Monitor user password:- dbsnmp/*******

Role:- NORMAL

Oracle Home path:-

Listener Machine name:-

Port:-

SID:-

Click on Next.

Click on summit.

click on close.

DATABASE HOST ADD SUCCESSFULLY DONE ON OEM13C.

there are no active responsibilities available for this user oracle apps r12

There are no Active Responsibilities available for this User

Solution:-

1. Login with sysadmin.

2. Query up the user (that is having the issue) and ensure responsibilities not showing up are NOT end dated.

3. END DATE the USER (not the responsibility) and save the record.

4. UN-END DATE the USER and save the record.

5 Request Name = Workflow Directory Services User/Role Validation
Batch Size = 10000
User name = SJHA
Fix dangling users = Yes
Add missing user/role assignments = Yes
Update WHO columns in WF tables = YES
Click "OK" and "Submit".

6. Clear the Cache

7. Missing responsibilities now appear.

Issue resolved.

Argument list too long

EM12c, EM13c: Cloud Control Agent Installation On RHEL 7 Machine
Fails With "/bin/uname: Argument list too long" (Doc ID 2281440.1)

Error find from BI log file.

Enterprise Manager Cloud Control running the command "/apps/middleware/bin/emctl stop oms -all -force -debug".

APPLIES TO:

Enterprise Manager Base Platform - Version 12.1.0.4.0 and later
Information in this document applies to any platform.
SYMPTOMS

Agent installation on RHEL 7 machine using push method from OEM cloud control or using silent
method fails at agent deployment with following error in agentDeploy_<timestamp>.log:

================
Cloning the agent home...
INFO: /opt/app/OracleHomes/agent_13.1.0.0.0/bin/emctl: line 287: /usr/bin/uname: Argument list too long
INFO: /opt/app/OracleHomes/agent_13.1.0.0.0/bin/emctl: line 288: /usr/bin/uname: Argument list too long
INFO: /opt/app/OracleHomes/agent_13.1.0.0.0/bin/emctl: line 475: /opt/app/OracleHomes/agent_13.1.0.0.0/perl/bin/perl:
Argument list too long
================

CAUSE

Issue is due to stack guard page added to Linux kernel as mentioned by Red Hat in the following link:
https://access.redhat.com/security/vulnerabilities/stackguard?sc_cid=70160000000gzltAAA&

SOLUTION

Perform any of the following steps to resolve the issue:

Workaround 1:
==========

Kindly follow the below steps.
[+] Backup <MIDDLEWARE_HOME>/bin/commonenv [+] Increase the stack thread size (EM_THREAD_STACK_SIZE) in the commonenv file as described below:
from ===================================== if [ "$uname" = "Linux" ] ; then if [ "$EM_THREAD_STACK_SIZE" = "" ] ; then EM_THREAD_STACK_SIZE=3072 fi ulimit -S -s $EM_THREAD_STACK_SIZE
if [ "$EM_DONT_CHANGE_CORE_SIZE" = "" ] ; then ulimit -S -c hard fi fi =====================================
TO
===================================== if [ "$uname" = "Linux" ] ; then if [ "$EM_THREAD_STACK_SIZE" = "" ] ; then EM_THREAD_STACK_SIZE=8192 fi ulimit -S -s $EM_THREAD_STACK_SIZE
if [ "$EM_DONT_CHANGE_CORE_SIZE" = "" ] ; then ulimit -S -c hard fi fi
=====================================
[+] In bash profile of the operating system user (user performing the OMS installation), set the following parameter:

$ export EM_THREAD_STACK_SIZE=8192

[+] If the UI is still open, then please click on "Retry" and continue with the installation.

[+] If you accidentally exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script from the Oracle home to rerun the Configuration Assistant in silent mode. For Microsoft Windows platforms, invoke runConfig.bat script.

$<ORACLE_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<absolute_path_to_Oracle_home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}

a. In bash profile of the operating system user (user performing the agent installation .bash_profile, .bash_rc),

set the following parameter:
$ export EM_THREAD_STACK_SIZE=8192

b. Retry the agent installation

Workaround 2:
==========
As agent home will be created already as part of the agent installation process, so run the following command to
complete the agent installation:

a. In bash profile of the operating system user (user performing the agent installation .bash_profile, .bash_rc),
set the following parameter:
$ export EM_THREAD_STACK_SIZE=8192

b. Rename the agent instance (agent_inst) folder if exists

c. Configure the agent by running the following command:
$ cd <AGENT HOME>/sysman/install
$ ./agentDeploy.sh AGENT_BASE_DIR=<agent base directory> AGENT_INSTANCE_HOME=<agent instance home> OMS_HOST=<oms hostname> EM_UPLOAD_PORT=<oms upload port> > AGENT_REGISTRATION_PASSWORD=<agent registration password> -configOnly