Tuesday, September 17, 2013

Oracle 12c Cloud ORA-01017 and Changing 'SYSMAN' Password

 check the oms  logs  located in ;

            /u01/app/oracle/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out


make sure you get the error ORA-01017 in log file...

then stop all the OMS

/u01/app/oracle/Middleware/oms/bin/emctl stop oms

Modify the password of 'SYSMAN';

/u01/app/oracle/Middleware/oms/bin/emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd <Password of SYS> -new_pwd <New Password for SYSMAN>

output of the above command;

[oracle@emcloud bin]$ ./emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd oracle -new_pwd Password1


Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
Changing passwords in backend ...
Passwords changed in backend successfully.
Updating repository password in Credential Store...
Successfully updated Repository password in Credential Store.
Restart all the OMSs using 'emctl stop oms -all' and 'emctl start oms'.
Successfully changed repository password.

start all the OMS;

 /u01/app/oracle/Middleware/oms/bin/emctl start oms  


- Erol

Tuesday, August 20, 2013

Monday, June 17, 2013

EMCTL(Enterprise Manager) Invalid Connection Pool. ERROR = ORA-28000:




Check SYSMAN and DBSNMP account status...this problem can be related with wrong password configuration of emctl...

first check status of SYSMAN and DBSNMP;

select account_status,lock_date,username from dba_users where username in ('SYSMAN','DBSNMP');


ACCOUNT_STATUS                   LOCK_DATE       USERNAME
-------------------------------- --------------- ------------------------------
OPEN                                                                          DBSNMP
LOCKED(TIMED)                         17-06-13              SYSMAN

SYSMAN status LOCKED ...before unlocking sysman accout stop the dbconsole;

 emctl stop dbconsole

Then

 sqlplus / as sysdba

SQL> alter user sysman account unlock;
SQL> alter user sysman identified by  NEWPASSWORD;

and set password of emctl  with oracle user; and set dbconsole password as NEWPASSWORD

emctl setpasswd dbconsole
start dbconsole

emctl start dbconsole 


-Erol


Wednesday, June 12, 2013

TRUNCATE Aud$ table to prevent system tablespace from getting bigger...

My system tablespace was getting bigger everyday and i realized that  aud$ table was causing this problem and scheluding a  crontab-job truncating aud$ table on monday and thursday ..simply solved my problem..

with oracle user;

vi /home/oracle/scripts/truncate_aud_table.sh

then copy paste  into truncate_aud_table.sh

 #!/bin/bash
. /home/oracle/.bash_profile
output=`sqlplus -s "/ as sysdba" <<EOF
       set heading off feedback off verify off
       TRUNCATE TABLE aud$;
       exit
EOF
`
echo $output

after creating sh , give permissions

chmod 775  /home/oracle/scripts/truncate_aud_table.sh

and add it on crontab ;

00 15 * * 1,4 /home/oracle/scripts/audit_sil.sh > /home/oracle/scripts/audit_sil.log 2>&1


Will run on Monday and Thursday at 15:00 ..

Thursday, May 16, 2013

ASM file metadata operation (Non-Exadata)


    Today our developers were complaining about performance issue , and there were nothing special which could cause high cpu usage on server  but  there were many sessions with wait event "ASM file metadata operation" and "ksv master wait'"...after googling and digging the oracle support,  finally found doc id (1308282.1) related to problem with paramater "cell_offload_processing".. whydoes oracle use cell_offload_processing? 

     In Exadata Database Machine , Cell Offloading:The storage cells are saving the database node from processing some workload  to inside them..this process can be referred to as cell offloading...In a Non-Exadata Oracle database , when someone selects a single column in a row , entire block related to row will be writting from the disks to  buffer cache and then selected row will be extracted from this block..but Exadata database machine can pull desired rows from disks directly instead of writing entire block to buffer cache(this is also know as smart-scan)..Smart-scan can help to reduce I/O on database server.
  
     But in a Non-Exadata Oracle database, cell_offload_processing can be set as "FALSE" to solve this problem...

"alter system set cell_offload_processing = false;" 


This issue is also known as a bug and can be handled by applying Patch 
11800170...

- Erol


Thursday, May 9, 2013

Oracle Linux Desktop Gui Problem

You have to install these packages while installing oracle linux to have desktop gui...
"X Window System" , "Desktop General Purpose", "Desktop Graphical Administration Tools", "Legacy X Window System compatibility"
If u miss installing these packages.. u can install with yum
yum groupinstall "X Window System" Desktop "General Purpose Desktop" "Graphical Administration Tools" "Legacy X Window System compatibility"
if u dont have internet u need to install rpms manually from installation cd

-Erol

Thursday, April 18, 2013

ORA-12991: column is referenced in a multi-column constraint (Related to GoldenGate)

After moving our 10g database to 11g with golden gate...our developers were complaining about ORA-12991: column is referenced in a multi-column constraint...This problem is related to enabling Supplemental Logging with "ALTER DATABASE ADD SUPPLEMENTAL LOG DATA" , when u try to drop a column...First of all u have to find what  log_group_name causes the problem...

SQL> select log_group_name from dba_log_groups where table_name = 'TABLE_NAME' ;

LOG_GROUP_NAME
============================
GGS_DROP_COLS_24242


Then drop it;


SQL> alter table table_name drop supplemental log group GGS_DROP_COLS_24242;

table altered.



- Erol

Friday, April 5, 2013

re-executing root.sh when installation fails

rootcrs.pl -deconfig -force

how to set NLS_DATA_FORMAT on linux before starting rman

NLS_DATE_FORMAT='DD-MON-YYYY:HH24:MI:SS'; export NLS_DATE_FORMAT

 rman target sys/password

Creating user with dbms_metadata.get_ddl


select dbms_metadata.get_ddl('USER',username) from dba_users where username in ('user_1',user_2',user_3','user_4')


user_1,user_2,user_3,user_4 should be defined by dba as real user names...

Thursday, April 4, 2013