تجربیات اوراکلی و آموزش و ... در شهر اوراکل

۱۰ مطلب با موضوع «ORA» ثبت شده است

How To Keep Same Password For Oracle User When Its EXPIRED(GRACE) State

unlock کردن یوزر EXPIRED بدون تغییر رمز عبور آن.

 

Users’ passwords are valid for the duration of PASSWORD_LIFE_TIME in their profile. At the end of this period the password expires and must be changed. After the password expires, the user’s status will be in EXPIRED(GRACE) State until the day of PASSWORD_GRACE_TIME in the profile.

Detailed information about Oracle profiles can be found in the following article.

 

 

You can create the necessary command with the following query to change user status from EXPIRED (GRACE) to NORMAL by keeping the current password.

ادامه مطلب...
۰۲ اسفند ۰۰ ، ۱۰:۲۱ ۰ نظر موافقین ۰ مخالفین ۰
سعید حسینی فر

RAC GRID Root.sh ORA-27091 ORA-15081 unable to queue I/O

RAC GRID Root.sh ORA-27091 ORA-15081 unable to queue I/O

ERROR:

[root@node-01 install]# /u01/app/11.2.0/grid/root.sh
Running Oracle 11g root script...

The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME=  /u01/app/11.2.0/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params
LOCAL ADD MODE
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
OLR initialization - successful
Adding daemon to inittab
ACFS-9200: Supported
ACFS-9300: ADVM/ACFS distribution files found.
ACFS-9307: Installing requested ADVM/ACFS software.
ACFS-9308: Loading installed ADVM/ACFS drivers.
ACFS-9321: Creating udev for ADVM/ACFS.
ACFS-9323: Creating module dependencies - this may take some time.
ACFS-9327: Verifying ADVM/ACFS devices.
ACFS-9309: ADVM/ACFS installation correctness verified.
CRS-2672: Attempting to start 'ora.mdnsd' on 'node-01'
CRS-2676: Start of 'ora.mdnsd' on 'node-01' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'node-01'
CRS-2676: Start of 'ora.gpnpd' on 'node-01' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'node-01'
CRS-2672: Attempting to start 'ora.gipcd' on 'node-01'
CRS-2676: Start of 'ora.cssdmonitor' on 'node-01' succeeded
CRS-2676: Start of 'ora.gipcd' on 'node-01' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'node-01'
CRS-2672: Attempting to start 'ora.diskmon' on 'node-01'
CRS-2676: Start of 'ora.diskmon' on 'node-01' succeeded
CRS-2676: Start of 'ora.cssd' on 'node-01' succeeded

ASM created and started successfully.

Disk Group OCR_VOTE created successfully.

Errors in file :
ORA-27091: unable to queue I/O
ORA-15081: failed to submit an I/O operation to a disk
ORA-06512: at line 4
PROT-1: Failed to initialize ocrconfig
PROC-26: Error while accessing the physical storage
ORA-27091: unable to queue I/O
ORA-15081: failed to submit an I/O operation to a disk
ORA-06512: at line 4

Failed to create Oracle Cluster Registry configuration, rc 255
Oracle Clusterware Repository configuration failed at /u01/app/11.2.0/grid/crs/install/crsconfig_lib.pm line 6471.
/u01/app/11.2.0/grid/perl/bin/perl -I/u01/app/11.2.0/grid/perl/lib -I/u01/app/11.2.0/grid/crs/install /u01/app/11.2.0/grid/crs/install/rootcrs.pl execution failed
[root@node-01 install]#



Solution:

The ASM Lib configuration was done with oracle id,But the grid installation i am doing with grid user.

[root@node-02 11202stage]# /usr/sbin/oracleasm configure
ORACLEASM_ENABLED=true
ORACLEASM_UID=oracle
ORACLEASM_GID=dba
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=""
ORACLEASM_SCANEXCLUDE=""
ORACLEASM_USE_LOGICAL_BLOCK_SIZE="false"

[root@node-02 11202stage]#

Update the configuration of ASMlib

/usr/sbin/oracleasm configure -u grid 

[root@node-02 11202stage]# /usr/sbin/oracleasm configure
ORACLEASM_ENABLED=true
ORACLEASM_UID=grid
ORACLEASM_GID=asmadmin
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=""
ORACLEASM_SCANEXCLUDE=""
ORACLEASM_USE_LOGICAL_BLOCK_SIZE="false"

[root@node-02 11202stage]#

For fresh installation delete the Disk group at asmlib.

/usr/sbin/oracleasm deletedisk OCR_VOTE01
/usr/sbin/oracleasm deletedisk ASM_DATA01
/usr/sbin/oracleasm deletedisk ASM_FRA01

And Recreate

/usr/sbin/oracleasm createdisk OCR_VOTE01 /dev/sde1
/usr/sbin/oracleasm createdisk ASM_DATA01 /dev/sdf1

/usr/sbin/oracleasm createdisk ASM_FRA01 /dev/sdg1

/usr/sbin/oracleasm listdisks

/usr/sbin/oracleasm scandisks

Now rerun the root.sh

 

 

http://oracletechdba.blogspot.com/2014/09/rac-grid-rootsh-ora-27091-ora-15081.html

۱۶ آبان ۹۹ ، ۱۵:۰۷ ۰ نظر موافقین ۰ مخالفین ۰
سعید حسینی فر

DBCA Does Not Display ASM Disk Groups In 12cR2

I was installing Oracle 12c R2 with ASM but somehow the DBCA did not list ASM diskgroups. After struggling for hours, I could find a solution, not sure if it is approved by Oracle but it works !!

 

Problem

 

I’ve installed Grid infrastructure with user grid, and I was trying to install oracle database 12cr2 with oracle user but during this installation I wasn’t able to see any of my ASM disk in the select disk group.

 

Solution

 

log in as root user

 

/dev/oracleasm/

ls -lrt to check the permission on oracleasm directory

chown -R grid:oinstall oracleasm

 

cd /dev/oracleasm/disks

 

Login as grid user

 

cd $ORACLE_HOME

cd bin

ls -ld to check the permision on oracle directory

chmod 6571 oracle

ls -ld oracle

 

Login as oracle user

 

cd $ORACLE_HOME

cd bin

ls -ld oracle to check the permision

 

However, oracle directory permision in both grid user and oracle user must have the same permission. Therefore, issue the following command;

 

chmod 6571 oracle

 

Go back to select disk group and refresh.

 

۰۹ آبان ۹۹ ، ۱۱:۵۳ ۰ نظر موافقین ۰ مخالفین ۰
سعید حسینی فر

DBSNMP Account Locked ORA-28000 in the Standby Database

 

This is because the standby is open read-only and cannot update any tables.
When a user's account has to be locked on the standby database, it is locked only in memory there.

 

ادامه مطلب...
۰۵ آذر ۹۸ ، ۰۸:۵۶ ۰ نظر موافقین ۰ مخالفین ۰
سعید حسینی فر

OEM13c – The page has expired. Click OK to continue.

If you are getting an error message or Pop-UP which says “The page has expired. Click OK to continue.” This means that your Cloud Control session has expired or timeout as there was no activity in your session.

 

The default value for session timeout is 45 minutes. Can we increase this session timeout frame, YES! You can. You set this value as per requirement of your company’s security policy. It may vary for different clients or companies.

 

As per your requirement you can increase the Session Timeout time by changing the value of “oracle.sysman.eml.maxInactiveTime” parameter. Also note that the value for this parameter is always defined in Minutes. In-my case the requirement was to keep the session active unless the user itself does not logs out from the application. So I set the value of oracle.sysman.eml.maxInactiveTime” parameter to -1. But if let’s say you want the session to be active for 10 hours you can set the value to 600. However if you want your session be active forever like in my case, you can set its value to -1.

NOTE: Zero means that the value is set to default than 45 minutes.

ادامه مطلب...
۰۲ مهر ۹۸ ، ۰۹:۱۱ ۰ نظر موافقین ۰ مخالفین ۰
سعید حسینی فر

RMAN-08137: WARNING: archived log not deleted, needed for standby

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

 
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
When we are taking archive log backup with delete then got an error.
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/pac/lci9t1/arch/redo_1_16470_842608348.arc thread=1 sequence=16470
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/pac/lci9t1/arch/redo_1_16471_842608348.arc thread=1 sequence=16471
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
ادامه مطلب...
۰۹ شهریور ۹۸ ، ۰۹:۳۰ ۰ نظر موافقین ۰ مخالفین ۰
سعید حسینی فر

ORA-12012,ORA-20001 AND ORA-06512 FROM ORA$AT_OS_OPT_SY_XXX

Problem :

========

ORA-12012: error on auto execute of job “SYS”.”ORA$AT_OS_OPT_SY_936″
ORA-20001: Statistics Advisor: Invalid task name for the current user
ORA-06512: at “SYS.DBMS_STATS”, line 47207
ORA-06512: at “SYS.DBMS_STATS_ADVISOR”, line 882
ORA-06512: at “SYS.DBMS_STATS_INTERNAL”, line 20059
ORA-06512: at “SYS.DBMS_STATS_INTERNAL”, line 22201
ORA-06512: at “SYS.DBMS_STATS”, line 47197
2017-03-13T00:47:21.394481+00:00

Cause :
========

This issue is happening because of the unavailability of the Stats Advisor Tasks from the created database.

Resolution :
=============

1. Connect to the created database using the SYSDBA privilege and run the following command:
2.

SQL>select name, ctime, how_created
from sys.wri$_adv_tasks
where owner_name = ‘SYS’
and name in (‘AUTO_STATS_ADVISOR_TASK’,’INDIVIDUAL_STATS_ADVISOR_TASK’);

no rows selected

3.

SQL> EXEC dbms_stats.init_package();

PL/SQL procedure successfully completed.

4.

SQL>select name, ctime, how_created
from sys.wri$_adv_tasks
where owner_name = ‘SYS’
and name in (‘AUTO_STATS_ADVISOR_TASK’,’INDIVIDUAL_STATS_ADVISOR_TASK’);

NAME                                                            CTIME             HOW_CREATED
——————–                                                —————–     ———————
AUTO_STATS_ADVISOR_TASK                  13-MAR-17       CMD
INDIVIDUAL_STATS_ADVISOR_TASK     13-MAR-17       CMD

 

5. Once the Stats Advisor Tasks are available in database, the database alert log no longer has: – ORA-06512 FROM ORA$AT_OS_OPT_SY_XXX

۱۴ مرداد ۹۸ ، ۰۸:۳۵ ۰ نظر موافقین ۰ مخالفین ۰
سعید حسینی فر

ORA-16072: a minimum of one standby database destination is required; ORA-03113: end-of-file on communication channel

 

 

اگر در بازیابی RMAN  با خطای زیر مواجه شدید و دیتابیس شاملStandby  و در مد Maximize Availability بود مراحل زیر را جهت رفع خطا دنبال کنید :

ORA-16072: a minimum of one standby database destination is required;

ORA-03113: end-of-file on communication channel

 

 

 

خطای بالا پس از تلاش برای OPEN کردن پایگاه ‌داده پس از Restore وRecover  RMAN رخ داده ‌است.

 

SQL> alter database open;

alter database open

*

ERROR at line 1:

ORA-03113: end-of-file on communication channel

Process ID: 3689

Session ID: 5644 Serial number: 5

 

در  RMAN بعد از open resetlogs:

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at

RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 17 and starting SCN of 822561

 


ادامه مطلب...
۱۰ فروردين ۹۸ ، ۱۰:۵۲ ۰ نظر موافقین ۱ مخالفین ۰
سعید حسینی فر

تغییر پسورد کاربر sys و برطرف کردن مشکل ORA-01017

 

     در صورتی که بخواهید به صورت remote به دیتابیس لاگین کنید به صورت زیر

sqlplus sys@tnsname as sysdba

     ممکن است با ارور ORA-01017 مواجه شوید. برای برطرف کردن این مشکل ابتدا مطمئن شوید که فایل پسورد در مسیر $ORACLE_HOME/dbs/orapwORACLE_SID وجود دارد. در صورتی که این فایل موجود بود به صورت زیر به دیتابیس لاگین شوید:

sqlplus / as sysdba

SQL> select * from v$pwfile_users;

 

no rows selected

 

SQL> show parameter remote_login

 

NAME                                 TYPE        VALUE

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

remote_login_passwordfile            string      EXCLUSIVE

ادامه مطلب...
۰۷ اسفند ۹۷ ، ۱۶:۱۴ ۰ نظر موافقین ۰ مخالفین ۰
naser shateri

ERROR: The Oracle Management Server (OMS) host and port specified via OMS_HOST & EM_UPLOAD_PORT is not available

اگر در مراحل deployment add host در Oracle Cloud 13 یا Oracle Cloud 12

ERROR: The Oracle Management Server (OMS) host and port specified via OMS_HOST & EM_UPLOAD_PORT is not available.
ERROR: The Oracle Management Server (OMS) host and port specified via
OMS_HOST & EM_UPLOAD_PORT is not available.Pass in a valid hostname
and port number for the OMS to successfully deploy the agent.

با خطای بالا مواجه شدید موارد زیر را مد نظر قرار بدید و حتماً بررسی کنید :

ادامه مطلب...
۱۸ بهمن ۹۷ ، ۱۳:۴۹ ۰ نظر موافقین ۱ مخالفین ۰
سعید حسینی فر