本文将介绍Navicat连接oracle时报ORA-28547错误的详细情况，特别是关于navicat连接oracle数据库报错的相关信息。我们将通过案例分析、数据研究等多种方式，帮助您更全面地了解这
本文将介绍Navicat 连接 oracle 时 报 ORA-28547 错误的详细情况，特别是关于navicat连接oracle数据库报错的相关信息。我们将通过案例分析、数据研究等多种方式，帮助您更全面地了解这个主题，同时也将涉及一些关于19C impdp 导入报 ORA-39087,ORA-39070,ORA-39002 错误、DG不能自动mount导致数据库不能正常启动：ORA-01157、ORA-01110、ORA-17503、ORA-150、expdp导出报错：ORA-31626 ORA-31633 ORA-06512 ORA-01658怎么办、HP-UNIX 平台修改 Oracle processes 参数报错：ORA-27154、ORA-27300、ORA-27301、ORA-27302的知识。
本文目录一览：
Navicat 连接 oracle 时 报 ORA-28547 错误（navicat连接oracle数据库报错）
今天在用navicat for oracle的时候遇到ORA-28457，显示无法连接到数据库，提示如下：解决方案之ORA-28547" alt="Navicat 解决方案之ORA-28547" src="http://static.oschina.net/uploads/img/201301/25161827_yV2Q.jpg" width="640" height="161">
网上查了很多，也没找到详细的解决方法，后边结合多方面资料才找出原因。原来在navicat中要设置指定的文件。具体如下：打开安装好的navicat——”工具“菜单——”选项“——下边有个OCI的设置
设置如下：OCI library(oci.dll)* :设置为 D:\app\Administrator\product\11.2.0\client_1\BIN\oci.dll
SQL *Plus设置为 D:\app\Administrator\product\11.2.0\client_1\BIN\sqlplus.exe
注：我的oracle客户端安装目录是D:\app ，改的时候自己注意下。
修改完后保存，重新打开navicat 新建连接如图：
19C impdp 导入报 ORA-39087,ORA-39070,ORA-39002 错误
| [oracle@localhost ~]$ impdp system/oracle@wangjiapdb directory=dpdata1 dumpfile=wangjiapdb.dmp logfile=20190508.log full=y
Import: Release 19.0.0.0.0 - Production on Wed May 8 16:30:15 2019
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-39087: directory name DPDATA1 is invalid
报错原因未切换到 wangjiapdb 创建 DPDATA1 目录
重新创建 directory 目录
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 WANGJIAPDB READ WRITE NO
SQL> alter session set container=WANGJIAPDB;
Session altered.
SQL> select * from dba_directories
OWNER DIRECTORY_NAME DIRECTORY_PATH ORIGIN_CON_ID
---------- ------------------------------ -------------------------------------------------- -------------
SYS SDO_DIR_WORK /u01/app/oracle/product/19.3.0.1/db_1/work 1
SYS SDO_DIR_ADMIN /u01/app/oracle/product/19.3.0.1/db_1/md/admin 1
SYS XMLDIR /u01/app/oracle/product/19.3.0.1/db_1/rdbms/xml 1
SYS XSDDIR /u01/app/oracle/product/19.3.0.1/db_1/rdbms/xml/sc 1
hema
SYS OPATCH_INST_DIR /u01/app/oracle/product/19.3.0.1/db_1/OPatch 1
SYS ORACLE_OCM_CONFIG_DIR2 /u01/app/oracle/product/19.3.0.1/db_1/ccr/state 1
SYS ORACLE_BASE /u01/app/oracle 1
SYS ORACLE_HOME /u01/app/oracle/product/19.3.0.1/db_1 1
SYS ORACLE_OCM_CONFIG_DIR /u01/app/oracle/product/19.3.0.1/db_1/ccr/state 1
OWNER DIRECTORY_NAME DIRECTORY_PATH ORIGIN_CON_ID
---------- ------------------------------ -------------------------------------------------- -------------
SYS DATA_PUMP_DIR /u01/app/oracle/admin/orcl/dpdump/885C57ADCCED4ECA 1
E055000000000001
SYS OPATCH_SCRIPT_DIR /u01/app/oracle/product/19.3.0.1/db_1/QOpatch 1
SYS OPATCH_LOG_DIR /u01/app/oracle/product/19.3.0.1/db_1/rdbms/log 1
SYS JAVA$JOX$CUJS$DIRECTORY$ /u01/app/oracle/product/19.3.0.1/db_1/javavm/admin/ 1
13 rows selected.
PDB 下手工创建 directory dpdata1
SQL> create directory dpdata1 as ''/home/oracle/dumpdir'';
Directory created.
授予权限
SQL> grant read,write on directory dpdata1 to system;
Grant succeeded.
SQL> show con_name;
CON_NAME
------------------------------
WANGJIAPDB
再次执行导入成功
[oracle@localhost ~]$ impdp system/oracle@wangjiapdb directory=dpdata1 dumpfile=wangjiapdb.dmp logfile=20190508.log full=y
Import: Release 19.0.0.0.0 - Production on Wed May 8 16:34:41 2019
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
import done in AL32UTF8 character set and AL16UTF16 NCHAR character set
export done in AL32UTF8 character set and UTF8 NCHAR character set
Warning: possible data loss in character set conversions
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/********@wangjiapdb directory=dpdata1 dumpfile=wangjiapdb.dmp logfile=20190508.log full=y
Processing object type DATABASE_EXPORT/PRE_SYSTEM_IMPCALLOUT/MARKER
Processing object type DATABASE_EXPORT/PRE_INSTANCE_IMPCALLOUT/MARKER
Processing object type DATABASE_EXPORT/TABLESPACE
ORA-31684: Object type TABLESPACE:"UNDOTBS1" already exists
ORA-31684: Object type TABLESPACE:"TEMP" already exists
Processing object type DATABASE_EXPORT/PROFILE
Processing object type DATABASE_EXPORT/SYS_USER/USER
ORA-31685: Object type USER:"SYS" failed due to insufficient privileges. Failing sql is:
ALTER USER "SYS" IDENTIFIED BY VALUES ''S: ;T: '' TEMPORARY TABLESPACE "TEMP"
Processing object type DATABASE_EXPORT/SCHEMA/USER
Processing object type DATABASE_EXPORT/RADM_FPTM
Processing object type DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
ORA-39083: Object type DEFAULT_ROLE:"C##ZQ" failed to create with error:
ORA-01918: user ''C##ZQ'' does not exist
Failing sql is:
ALTER USER "C##ZQ" DEFAULT ROLE ALL
ORA-39083: Object type DEFAULT_ROLE:"SPATIAL_CSW_ADMIN_USR" failed to create with error:
ORA-01918: user ''SPATIAL_CSW_ADMIN_USR'' does not exist
Failing sql is:
ALTER USER "SPATIAL_CSW_ADMIN_USR" DEFAULT ROLE ALL
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
ORA-31684: Object type DIRECTORY:"DPDATA1" already exists
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
>>> Cannot set an SCN larger than the current SCN. If a Streams Capture configuration was imported then the Apply that processes the captured messages needs to be dropped and recreated. See My Oracle Support article number 1380295.1.
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PROCOBJ
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
ORA-31625: Schema SPATIAL_CSW_ADMIN_USR is needed to import this object, but is unaccessible
ORA-01435: user does not exist
Failing sql is:
BEGIN
sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT(''USERENV'',''CURRENT_SCHEMA''), export_db_name=>''WANGJIAPDB'', inst_scn=>''2201360'');COMMIT; END;
ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
ORA-31625: Schema C##ZQ is needed to import this object, but is unaccessible
ORA-01435: user does not exist
Failing sql is:
BEGIN
sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT(''USERENV'',''CURRENT_SCHEMA''), export_db_name=>''WANGJIAPDB'', inst_scn=>''2201360'');COMMIT; END;
Processing object type DATABASE_EXPORT/EARLY_OPTIONS/VIEWS_AS_TABLES/TABLE
Processing object type DATABASE_EXPORT/EARLY_OPTIONS/VIEWS_AS_TABLES/TABLE_DATA
. . imported "SYS"."KU$_EXPORT_USER_MAP" 6.085 KB 38 rows
Processing object type DATABASE_EXPORT/EARLY_POST_INSTANCE_IMPCALLOUT/MARKER
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/TABLE
ORA-39342: Internal error - failed to import internal objects tagged with ORDIM due to ORA-00955: name is already used by an existing object
.
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/TABLE_DATA
. . imported "SYSTEM"."REDO_DB_TMP" 25.58 KB 1 rows
. . imported "WMSYS"."E$WORKSPACES_TABLE$" 12.10 KB 1 rows
. . imported "WMSYS"."E$HINT_TABLE$" 9.984 KB 97 rows
. . imported "WMSYS"."E$WORKSPACE_PRIV_TABLE$" 7.078 KB 11 rows
. . imported "SYS"."AMGT$DP$DAM_CONFIG_PARAM$" 6.523 KB 14 rows
. . imported "SYS"."DP$TSDP_SUBPOL$" 6.320 KB 1 rows
. . imported "WMSYS"."E$NEXTVER_TABLE$" 6.367 KB 1 rows
. . imported "WMSYS"."E$ENV_VARS$" 6.015 KB 3 rows
. . imported "SYS"."DP$TSDP_PARAMETER$" 5.945 KB 1 rows
. . imported "SYS"."DP$TSDP_POLICY$" 5.914 KB 1 rows
. . imported "WMSYS"."E$VERSION_HIERARCHY_TABLE$" 5.976 KB 1 rows
. . imported "WMSYS"."E$EVENTS_INFO$" 5.812 KB 12 rows
. . imported "LBACSYS"."OLS_DP$OLS$AUDIT" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$COMPARTMENTS" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$GROUPS" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$LAB" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$LEVELS" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$POL" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$POLS" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$POLT" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$PROFILE" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$PROG" 0 KB 0 rows
. . imported "LBACSYS"."OLS_DP$OLS$USER" 0 KB 0 rows
. . imported "SYS"."AMGT$DP$AUD$" 0 KB 0 rows
. . imported "SYS"."AMGT$DP$DAM_CLEANUP_EVENTS$" 0 KB 0 rows
. . imported "SYS"."AMGT$DP$DAM_CLEANUP_JOBS$" 0 KB 0 rows
. . imported "SYS"."DP$TSDP_ASSOCIATION$" 0 KB 0 rows
. . imported "SYS"."DP$TSDP_CONDITION$" 0 KB 0 rows
. . imported "SYS"."DP$TSDP_FEATURE_POLICY$" 0 KB 0 rows
. . imported "SYS"."DP$TSDP_PROTECTION$" 0 KB 0 rows
. . imported "SYS"."DP$TSDP_SENSITIVE_DATA$" 0 KB 0 rows
. . imported "SYS"."DP$TSDP_SENSITIVE_TYPE$" 0 KB 0 rows
. . imported "SYS"."DP$TSDP_SOURCE$" 0 KB 0 rows
. . imported "SYSTEM"."REDO_LOG_TMP" 0 KB 0 rows
. . imported "WMSYS"."E$BATCH_COMPRESSIBLE_TABLES$" 0 KB 0 rows
. . imported "WMSYS"."E$CONSTRAINTS_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$CONS_COLUMNS$" 0 KB 0 rows
. . imported "WMSYS"."E$LOCKROWS_INFO$" 0 KB 0 rows
. . imported "WMSYS"."E$MODIFIED_TABLES$" 0 KB 0 rows
. . imported "WMSYS"."E$MP_GRAPH_WORKSPACES_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$MP_PARENT_WORKSPACES_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$NESTED_COLUMNS_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$RESOLVE_WORKSPACES_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$RIC_LOCKING_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$RIC_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$RIC_TRIGGERS_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$UDTRIG_DISPATCH_PROCS$" 0 KB 0 rows
. . imported "WMSYS"."E$UDTRIG_INFO$" 0 KB 0 rows
. . imported "WMSYS"."E$VERSION_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$VT_ERRORS_TABLE$" 0 KB 0 rows
. . imported "WMSYS"."E$WORKSPACE_SAVEPOINTS_TABLE$" 0 KB 0 rows
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/VIEWS_AS_TABLES/TABLE
Processing object type DATABASE_EXPORT/NORMAL_OPTIONS/VIEWS_AS_TABLES/TABLE_DATA
. . imported "MDSYS"."RDF_PARAM$TBL" 6.507 KB 3 rows
. . imported "SYS"."AMGT$DP$AUDTAB$TBS$FOR_EXPORT" 5.953 KB 2 rows
. . imported "SYS"."DP$DBA_SENSITIVE_DATA" 0 KB 0 rows
. . imported "SYS"."DP$DBA_TSDP_POLICY_PROTECTION" 0 KB 0 rows
. . imported "SYS"."AMGT$DP$FGA_LOG$FOR_EXPORT" 0 KB 0 rows
. . imported "SYS"."NACL$_ACE_IMP" 0 KB 0 rows
. . imported "SYS"."NACL$_HOST_IMP" 6.914 KB 1 rows
. . imported "SYS"."NACL$_WALLET_IMP" 0 KB 0 rows
. . imported "SYS"."DATAPUMP$SQL$TEXT" 0 KB 0 rows
. . imported "SYS"."DATAPUMP$SQL$" 0 KB 0 rows
. . imported "SYS"."DATAPUMP$SQLOBJ$AUXDATA" 0 KB 0 rows
. . imported "SYS"."DATAPUMP$SQLOBJ$DATA" 0 KB 0 rows
. . imported "SYS"."DATAPUMP$SQLOBJ$PLAN" 0 KB 0 rows
. . imported "SYS"."DATAPUMP$SQLOBJ$" 0 KB 0 rows
. . imported "SYSTEM"."SCHEDULER_JOB_ARGS_TMP" 0 KB 0 rows
. . imported "SYSTEM"."SCHEDULER_PROGRAM_ARGS_TMP" 9.515 KB 12 rows
. . imported "WMSYS"."E$EXP_MAP" 7.710 KB 3 rows
. . imported "WMSYS"."E$METADATA_MAP" 0 KB 0 rows
Processing object type DATABASE_EXPORT/NORMAL_POST_INSTANCE_IMPCALLOUT/MARKER
Processing object type DATABASE_EXPORT/FINAL_POST_INSTANCE_IMPCALLOUT/MARKER
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
Processing object type DATABASE_EXPORT/AUDIT_UNIFIED/AUDIT_POLICY_ENABLE
Processing object type DATABASE_EXPORT/POST_SYSTEM_IMPCALLOUT/MARKER
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 9 error(s) at Wed May 8 16:38:58 2019 elapsed 0 00:04:12
[oracle@localhost ~]$ 重庆思庄 2019 年 12 月 30 日 OCP 脱产班即将开课，2020 年 2 月 15 日 OCP 周末班火热报名中，循环开课，欢迎联系试听！更多详情请访问思庄网站咨询课程老师！
|
DG不能自动mount导致数据库不能正常启动：ORA-01157、ORA-01110、ORA-17503、ORA-150
DG不能自动mount导致数据库不能正常启动：ORA-01157、ORA-01110、ORA-17503、ORA-15001、ORA-15001现象：每次重启整个CRS之后，D
dg不能自动mount导致数据库不能正常启动：ora-01157、ora-01110、ora-17503、ora-15001、ora-15001
现象：
每次重启整个crs之后，db都不能自动开启到open状态，查看alert日志报错：
success: diskgroup unid was mounted
thu nov 14 21:46:01 2013
create relation sweeperr
setting recovery target incarnation to 1
successful mount of redo thread 1, with mount id 2364838615
database mounted in exclusive mode
lost write protection disabled
completed: alter database mount
thu nov 14 21:46:05 2013
alter database open migrate
errors in file /opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ora-01157: cannot identify/lock data file 21 - see dbwr trace file
ora-01110: data file 21: ''+indx/nc/datafile/indx.256.820323481''
ora-17503: ksfdopn:2 failed to open file +indx/nc/datafile/indx.256.820323481
ora-15001: diskgroup "indx" does not exist or is not mounted
ora-15001: diskgroup "indx" does not exist or is not mounted
errors in file /opt/app/diag/rdbms/nc/nc1/trace/nc1_dbw0_8399.trc:
ora-01157: cannot identify/lock data file 22 - see dbwr trace file
ora-01110: data file 22: ''+indx/nc/datafile/indx.257.820323659''
ora-17503: ksfdopn:2 failed to open file +indx/nc/datafile/indx.257.820323659
ora-15001: diskgroup "indx" does not exist or is not mounted
从alert日志可以看出，indx dg的文件不能被读到，
查看发现indx dg处于dismount状态。
分析：
ASM中创建了2个DG：UNID,INDX.每次只有UNID会被自动mount,而INDX不能被自动MOUNT。
查看asm_diskgroups参数发现只设置了UNID，，这就是为什么每次INDX不会被自动MOUNT的原因了。
SQL>
SQL> show parameter asm
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups string UNID
SQL> show parameter pfile
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string
解决办法：
将INDX添加到asm_diskgroups参数中。
spfile:alter system set asm_diskgroups=''UNID'',''INDX'' scope=both;
pfile:修改pfile中asm_diskgroups参数。
相关阅读：
ORA-01172、ORA-01151错误处理
ORA-00600 [2662]错误解决
ORA-01078 和 LRM-00109 报错解决方法
ORA-00471 处理方法笔记
ORA-00314,redolog 损坏，或丢失处理方法
ORA-00257 归档日志过大导致无法存储的解决办法
expdp导出报错：ORA-31626 ORA-31633 ORA-06512 ORA-01658怎么办
expdp导出报错：ORA-31626 ORA-31633 ORA-06512 ORA-01658怎么办，很多新手对此不是很清楚，为了帮助大家解决这个难题，下面小编将为大家详细讲解，有这方面需求的人可以来学习下，希望你能有所收获。
ORA-31626：JOB does not exist
ORA-31633:unable to create master table "NYFS.SYS_EXPORT_SCHEMA_49"
ORA-06512:at "SYS.DBMS_SYS_ERROR" line 95
ORA-06518: unable to create INITIAL extent for segment in tablespace users
解决方案：由于表空间无自动扩展，USERS表空间已经占满，扩大USERS表空间即可。
ALTER DATABASE DATAFILE ''/XXX/XXX/USER01.DBF'' RESIZE 10G;
ALTER DATABASE DATAFILE ''/XXX/XXX/USER01.DBF'' AUTOEXTEND ON NEXT 50M MAXSIZE 10G;
看完上述内容是否对您有帮助呢？如果还想对相关知识有进一步的了解或阅读更多相关文章，请关注小编行业资讯频道，感谢您对小编的支持。
HP-UNIX 平台修改 Oracle processes 参数报错：ORA-27154、ORA-27300、ORA-27301、ORA-27302
OS 版本 ：HP-UX B.11.31
Oracle 版本：11.2.0.4 (RAC)
（一）问题描述
最近发现无法连接上数据库，报错信息为 “ORA-00020：maximum number of processes (3000) exceeded”，很明显是数据库的进程数量已经达到了最大值，可用过 v$process 确认
SQL> select count(*) from v$process;
COUNT(*)
----------
3000
于是打算将数据库参数 processes 改大一些，直接修改为 6000。修改命令如下：
SQL> alter system set processes=6000 scope=spfile sid=''*'';
重启节点：
srvctl stop instance -d {oracle_name} -i {instance_name}
srvctl start instance -d {oracle_name} -i {instance_name}
在重启时候，发现有错误提示：
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occurred at: sskgpcreates
（二）解决方案
通过查找资料，可通过修改 OS 内核参数解决，可以使用 SAM 修改，也可使用 kctune 工具修改，这里使用 kctune 工具修改，修改过程如下
（1）确认 semm * 参数的当前值
oracledb2#[/]kctune | grep semm
semmni 5120 5120
semmns 8192 8192
semmnu 4092 4092
semmsl 2048 Default Immed
（2）修改 semmni 参数
oracledb2#[/]kctune semmni=8192
==> Update the automatic ''backup'' configuration first? y
* The automatic ''backup'' configuration has been updated.
* Future operations will update the backup without prompting.
NOTE: The requested changes could not be applied to the currently
running system, for the following reasons:
- The tunable ''semmni'' cannot be changed without a reboot.
* The requested changes have been saved, and will take effect at
next boot.
Tunable Value Expression
semmni (now) 5120 5120
(next boot) 8192 8192
（3）修改 semmns 的值
oracledb2#[/]kctune semmns=16384
* The automatic ''backup'' configuration has been updated.
NOTE: The requested changes could not be applied to the currently
running system, for the following reasons:
- The tunable ''semmns'' cannot be changed without a reboot.
* The requested changes have been saved, and will take effect at
next boot.
Tunable Value Expression
semmns (now) 8192 8192
(next boot) 16384 16384
（4）修改 nproc 参数的值，该参数修改后立刻生效
oracledb2#[/]kctune nproc=8192
* The automatic ''backup'' configuration has been updated.
WARNING: The validity of the tunable values could not be completely
verified, because the value of the tunable ''process_id_max''
will not be known until the system is booted. The tunable
values will be verified during boot. Please check the console
messages during boot to see if there are any tunable value
errors.
* The requested changes have been applied to the currently
running configuration.
Tunable Value Expression Changes
nproc (before) 6144 6144 Immed
(now) 8192 8192
（5）修改 semmnu 的值
oracledb2#[/]kctune semmnu=8188
* The automatic ''backup'' configuration has been updated.
NOTE: The requested changes could not be applied to the currently
running system, for the following reasons:
- The tunable ''semmnu'' cannot be changed without a reboot.
* The requested changes have been saved, and will take effect at
next boot.
Tunable Value Expression
semmnu (now) 4092 4092
(next boot) 8188 8188
需要注意的是，在修改 semmnu 之前，需要确定 nproc 的值，确保：nproc >= semmnu + 4。
错误示范：
oracledb2#[/]kctune semmnu=8188
ERROR: The values of the tunables ''semmnu'' (8188) and ''nproc'' (6144)
do not satisfy the requirement:
nproc >= semmnu + 4
在改完参数之后，需要重启 OS，参数才能生效。接着再重启数据库，正常启动。
今天关于Navicat 连接 oracle 时 报 ORA-28547 错误和navicat连接oracle数据库报错的介绍到此结束，谢谢您的阅读，有关19C impdp 导入报 ORA-39087,ORA-39070,ORA-39002 错误、DG不能自动mount导致数据库不能正常启动：ORA-01157、ORA-01110、ORA-17503、ORA-150、expdp导出报错：ORA-31626 ORA-31633 ORA-06512 ORA-01658怎么办、HP-UNIX 平台修改 Oracle processes 参数报错：ORA-27154、ORA-27300、ORA-27301、ORA-27302等更多相关知识的信息可以在本站进行查询。
