RMAN-06403: could not obtain a fully authorized session
使用rman進行資料庫恢復時出現如下錯誤:
[oracle@localhost dbs]$ rman target / nocatalog;
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Oct 21 00:52:38 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> restore database;
Starting restore at 21-OCT-14
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/21/2014 00:52:46
RMAN-12010: automatic channel allocation initialization failed
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
出現這個錯誤的原因是我的資料庫對應有兩個例項,而我沒有指定例項,透過export指定例項之後問題解決:
[oracle@localhost dbs]$ rman target / nocatalog;
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Oct 21 00:52:38 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> restore database;
Starting restore at 21-OCT-14
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 10/21/2014 00:52:46
RMAN-12010: automatic channel allocation initialization failed
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
出現這個錯誤的原因是我的資料庫對應有兩個例項,而我沒有指定例項,透過export指定例項之後問題解決:
[oracle@localhost dbs]$ export ORACLE_SID=orcl
[oracle@localhost dbs]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Oct 21 00:58:06 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1383986269, not open)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_orcl.f'; # default
[oracle@localhost dbs]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Oct 21 00:58:06 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1383986269, not open)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_orcl.f'; # default
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29800581/viewspace-1307232/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Could not obtain transaction-synchronized Session for current thread原因及解決方案AIsynchronizedSessionthread
- 異常資訊解決:Could not obtain transaction-synchronized Session for current threadAIsynchronizedSessionthread
- su - xxx Could not create sessionSession
- Many To Many could not initialize proxy – no Session的解決方法Session
- Fully-developed Web AppdevWebAPP
- ERROR: MaxTemperature is not COMMAND nor fully qualified CLASSNAMEError
- FCOS: Fully Convolutional One-Stage Object DetectionObject
- 論文閱讀筆記:Fully Convolutional Networks for Semantic Segmentation筆記Segmentation
- MongoDB 檢視DDL檢視not authorized on xxx to execute command { find: system.viewsMongoDBZedView
- 求助:環境正常,xcodebuild 也執行成功了,但是使用 appium desktop 的時候,出現:Could not start sessionXCodeUIAPPSession
- org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection 解決辦法SpringFrameworkJDBCOTGExceptionAI
- 詳解PyTorch FSDP資料並行(Fully Sharded Data Parallel)PyTorch並行Parallel
- SciTech-Mathmatics-Probability+Statistics-Population Vs. Sampling: Representative Samples + How to obtain SamplesAI
- Improved Security for a Ring-Based Fully Homomorphic Encryption Scheme-2013:解讀Scheme
- apt could not get lockAPT
- laravel session 與 php session配置LaravelSessionPHP
- session和v$session說明Session
- SessionSession
- Connection could not be established with host 求救
- session switchSession
- session 共享Session
- cookie sessionCookieSession
- cookie & sessionCookieSession
- Session案例Session
- Spring SessionSpringSession
- Cloud Foundry Session Affinity(Sticky Session)的實現CloudSession
- ubuntu : xcb:could not connect to display.Ubuntu
- iOS逆向之三 authorized_keys ssh登入越獄手機免驗證設定iOSZed
- 從koa-session原始碼解讀session原理Session原始碼
- [20180918]disconnect session和kill session的區別.txtSession
- cookie&sessionCookieSession
- Cookie和SessionCookieSession
- session和cookieSessionCookie
- session測試Session
- Media Session APISessionAPI
- R session AbortedSession
- drools session理解Session
- Oracle session traceOracleSession
- Session 簡介Session