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.

Thursday, 10 August 2017

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.

Tuesday, 1 August 2017

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



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.