Смотри на предмет наличия динамического SQL в исполняемом коде пакета, возможно там используется что-то, чего уже нет.
Если следующая ошибка в стеке ошибок ORA-04065, скорее всего динамический код использует объект, который был изменен/ревалидирован в течении жизни сессии.
TaNK
Дата 28.8.2013, 09:00 (ссылка) | (нет голосов) Загрузка .
Опытный
Профиль Группа: Участник Сообщений: 669 Регистрация: 29.10.2006 Где: Краснодар
Репутация: нет Всего: 1
Zloxa
Дата 28.8.2013, 10:34 (ссылка) | (нет голосов) Загрузка .
Дата 28.8.2013, 21:25 (ссылка) | (нет голосов) Загрузка .
Опытный
Профиль Группа: Участник Сообщений: 669 Регистрация: 29.10.2006 Где: Краснодар
Репутация: нет Всего: 1
Данный раздел предназначен для обсуждения проблем с Oracle Database, другие продукты Oracle здесь не обсуждаются. Просьба при создании темы, придерживаться следующих правил:
при создании темы давайте ей осмысленное название, описывающее суть проблемы
указывайте используемую версию базы, способ соединения и язык программирования
при ошибках обязательно приводите код ошибки и сообщение сервера
приводите код в котором возникла ошибка, по возможности дайте тестовый пример демонстрирующий ошибку
при вставке кода используйте соответсвующие теги: [code=sql] [/code] для подсветки SQL и PL/SQL кода, [code=java] [/code] — для Java, и т.д.
документация по Oracle: 9i, 10g, 11g
книги по Oracle можно поискать здесь
действия модераторов можно обсудить здесь
Если Вам понравилась атмосфера форума, заходите к нам чаще! С уважением, Zloxa, LSD.
0 Пользователей читают эту тему (0 Гостей и 0 Скрытых Пользователей)
0 Пользователей:
« Предыдущая тема | Oracle | Следующая тема »
[ Время генерации скрипта: 0.1099 ] [ Использовано запросов: 21 ] [ GZIP включён ]
Enter the following information: Database SID: PROD10 Listener port number: 1531 Password for SYS user: Password for SYSMAN user:
———————————————————————- WARNING : While repository is dropped the database will be put in quiesce mode. ———————————————————————- Do you wish to continue? [yes(Y)/no(N)]: y 11.07.2013 19:09:18 oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_2013_07_11_19_08_54.log. 11.07.2013 19:09:20 oracle.sysman.emcp.EMDBPreConfig performDeconfiguration WARNING: EM is not configured for this database. No EM-specific actions can be performed. Some of the possible reasons may be: 1) EM is configured with different hostname then physical host. Set environment variable ORACLE_HOSTNAME= and re-run EMCA script 2) ORACLE_HOSTNAME is set. Unset it and re-run EMCA script 11.07.2013 19:09:20 oracle.sysman.emcp.EMReposConfig invoke INFO: Dropping the EM repository (this may take a while) . 11.07.2013 19:09:22 oracle.sysman.emcp.util.PlatformInterface executeCommand WARNING: Error executing /u1/oracle/PROD10/db/tech_st/11.2.0/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=sun5140)(PORT=1531)))(CONNECT_DATA=(SERVICE_NAME=PROD10))) -repos_user SYSMAN -action drop -verbose -output_file /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_repos_drop_2013_07_11_19_09_20.log 11.07.2013 19:09:22 oracle.sysman.emcp.EMReposConfig invoke SEVERE: Error dropping the repository 11.07.2013 19:09:22 oracle.sysman.emcp.EMReposConfig invoke INFO: Refer to the log file at /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_repos_drop_ .log for more details. 11.07.2013 19:09:22 oracle.sysman.emcp.EMConfig perform SEVERE: Error dropping the repository Refer to the log file at /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_2013_07_11_19_08_54.log for more details. Could not complete the configuration. Refer to the log file at /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_2013_07_11_19_08_54.log for more details.
���������� ��� ��-�� �����
�����
CONFIG: Enter SYS user’s password : Getting temporary tablespace from database. Could not connect to SYS/(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=sun5140)(PORT=1531)))(CONNECT_DATA=(SERVICE_NAME=PROD10))): ORA-01031: insufficient privileges (DBD ERROR: OCISessionBegin)
11.07.2013 19:09:22 oracle.sysman.emcp.util.PlatformInterface executeCommand CONFIG: stty: : No such device or address stty: : No such device or address
11.07.2013 19:09:22 oracle.sysman.emcp.util.PlatformInterface executeCommand WARNING: Error executing /u1/oracle/PROD10/db/tech_st/11.2.0/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=sun5140)(PORT=1531)))(CONNECT_DATA=(SERVICE_NAME=PROD10))) -repos_user SYSMAN -action drop -verbose -output_file /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_repos_drop_2013_07_11_19_09_20.log 11.07.2013 19:09:22 oracle.sysman.emcp.EMReposConfig invoke SEVERE: Error dropping the repository 11.07.2013 19:09:22 oracle.sysman.emcp.EMReposConfig invoke INFO: Refer to the log file at /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_repos_drop_ .log for more details. 11.07.2013 19:09:22 oracle.sysman.emcp.EMConfig perform SEVERE: Error dropping the repository Refer to the log file at /u1/oracle/PROD10/cfgtoollogs/emca/PROD10/emca_2013_07_11_19_08_54.log for more details. 11.07.2013 19:09:22 oracle.sysman.emcp.EMConfig perform CONFIG: Stack Trace: oracle.sysman.emcp.exception.EMConfigException: Error dropping the repository at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:230) at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:160) at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:253) at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:599) at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1482) at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:583) at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:529) 11.07.2013 19:09:22 oracle.sysman.emcp.EMConfig restoreOuiLoc CONFIG: Restoring oracle.installer.oui_loc to /u1/oracle/PROD10/db/tech_st/11.2.0/oui
� ���. DBUA �� ��������� Post Upgrade �� �����. Post Upgrade
�����
A persistent initialization parameter file (spfile) has been created at the following location: /u1/oracle/PROD10/db/tech_st/11.2.0/dbs/spfilePROD10.ora. Error ignored: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired ORA-06512: at «SYS.UTL_RECOMP», line 829 ORA-06512: at line 4
��������� ���������� �������:
�����
select substr(owner,1,12) owner, substr(object_name,1,30) object, 2 substr(object_type,1,30) type, status from dba_objects where status <>‘VALI D’;
OWNER OBJECT TYPE STATUS ———— —————————— ——————- ——- APPS PMI_REP_PROD_STATUS_V VIEW INVALID APPS OE_TAX_EXEMPTIONS_QP_V VIEW INVALID APPS IGW_BUDGET_CATEGORY_V VIEW INVALID APPS PO_CXML_LINE_LOC_ARCH_V VIEW INVALID APPLSYS WF_DEFERRED_R RULE SET INVALID APPS IGW_REPORT_PROCESSING PACKAGE BODY INVALID APPS IEX_BPD_CNSLD_INV_REMAINING_V VIEW INVALID APPS AR_CBA_EFT_USER_NUMBER_V VIEW INVALID APPS FEM_CHECK_BR_DIS_MBRS_PKG PACKAGE BODY INVALID SYS X_$KSLEI VIEW INVALID PUBLIC X$KSLEI SYNONYM INVALID
OWNER OBJECT TYPE STATUS ———— —————————— ——————- ——- SYS X_$KGLLK VIEW INVALID PUBLIC X$KGLLK SYNONYM INVALID APPS XXT_LOAD_HZ_PARTIES PACKAGE BODY INVALID PERFSTAT STATSPACK PACKAGE BODY INVALID APPS XXT_PERSONALIZATIONS_V VIEW INVALID
�������� @utlrp.sql
�����
SQL> @utlrp.sql
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid DOC> objects in the database. Recompilation time is proportional to the DOC> number of invalid objects in the database, so this command may take DOC> a long time to execute on a database with a large number of invalid DOC> objects. DOC> DOC> Use the following queries to track recompilation progress: DOC> DOC> 1. Query returning the number of invalid objects remaining. This DOC> number should decrease with time. DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6); DOC> DOC> 2. Query returning the number of objects compiled so far. This number DOC> should increase with time. DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED; DOC> DOC> This script automatically chooses serial or parallel recompilation DOC> based on the number of CPUs available (parameter cpu_count) multiplied DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu). DOC> On RAC, this number is added across all RAC nodes. DOC> DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel DOC> recompilation. Jobs are created without instance affinity so that they DOC> can migrate across RAC nodes. Use the following queries to verify DOC> whether UTL_RECOMP jobs are being created and run correctly: DOC> DOC> 1. Query showing jobs created by UTL_RECOMP DOC> SELECT job_name FROM dba_scheduler_jobs DOC> WHERE job_name like ‘UTL_RECOMP_SLAVE_%’; DOC> DOC> 2. Query showing UTL_RECOMP jobs that are running DOC> SELECT job_name FROM dba_scheduler_running_jobs DOC> WHERE job_name like ‘UTL_RECOMP_SLAVE_%’; DOC>#
PL/SQL procedure successfully completed.
DOC> The following query reports the number of objects that have compiled DOC> with errors (objects that compile with errors have status set to 3 in DOC> obj$). If the number is higher than expected, please examine the error DOC> messages reported with each object (using SHOW ERRORS) to see if they DOC> point to system misconfiguration or resource constraints that must be DOC> fixed before attempting to recompile these objects. DOC>#
DOC> The following query reports the number of errors caught during DOC> recompilation. If this number is non-zero, please query the error DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors DOC> are due to misconfiguration or resource constraints that must be DOC> fixed before objects can compile successfully. DOC>#