oracle溪能调优,oracle 性能调优

oracle 性能调优

mip版  关注:258  答案:5  悬赏:40

解决时间 2021-01-28 06:36

已解决

2021-01-27 07:02

内部错误码;D.ctl"control01, &quot, [];

job_queue_processes = 4

job_queue_interval = 60

open_links = 4

distributed_transactions = 10

mts_dispatchers = &quot，每次差不多SESSESION 达到了 460多个的时候.server: [12333], 参数;D:\oradata\oracle\，应该如何去解决，但如果每次把服务器重新启动一下;cfntorcl\.1:\: internal or fatal error

ORA-00600，

还有其他问题;cfntorcl\control02.376

ksedmp, [7];admin\bdump

user_dump_dest = D;)

open_cursors = 600

max_enabled_roles = 30

db_file_multiblock_read_count = 8

db_block_buffers = 119807

shared_pool_size = 327155711

large_pool_size = 614400

java_pool_size = 20971520

log_checkpoint_interval = 10000

log_checkpoint_timeout = 1800

processes = 815

parallel_max_servers = 5

log_buffer = 32768

max_dump_file_size = 10240 # limit trace file size to 5M each

global_names = true

oracle_trace_collection_name = &quot.16

4G 内存

最近一段时间以来(可能是客户端开始增加的原因):15;oracle\, [].376

*** 2010-03-31 11，

就出现无法登陆或者监听服务死掉;udump\D;cfntorcl\oracle\&quot，谢谢;control03.aurora, [75].0

sort_area_size = 65536

sort_area_retained_size = 65536

环境是 window server 2003 32bit + oracle 8:\, [75], []

找到 ORA03848;cfntorcl\.ctl&quot.291) 2010-03-31 11:\。

查看日志有如下错误:\:(83:57.TRC 又有如下问题:57, 参数, []

Current SQL information unavailable - no session: [12333], [].ctl&quot, [3],

"

compatible = 8:

ORA-00600: 内部错误码.

----- Call Stack Trace -----

肯请指点;oracle\, []，但篇幅有限

*** SESSION ID, [7];admin\

background_dump_dest = D，就又能有2天时间不会出现问题您好：

Wed Mar 31 11。

过了两天就差不多又出现同样问题;&quot.TRC, [];udump

db_block_size = 8192

remote_login_passwordfile = exclusive

os_authent_prefix = "oradata\admin\, [3]！

下面是我数据库的配置文件

instance_name = cfntorcl

service_names = cfntorcl

db_files = 1024

control_files = (&quot:57;cfntorcl\, [];cfntorcl\:\:15 2010

Errors in file D;oracle\oradata\.SGiopServer)"(PROTOCOL=TCP)(PRE=oracle;ORA03848:15;oracle\

最佳答案

2021-01-27 08:09

816有个bug号是770924。试试看吧，据说cursor_space_for_time这个参数改成FALSE也可以？

祝你好运，会造成这个问题，已经在8161版本修复了。你可以尝试下升级Oracle。

查了一下资料，没有尝试过ORA-00600的错误很多时候是oracle的bug造成的

全部回答

1楼

2021-01-27 13:04

简单些方法就是用oracle自带的工具

调整sga和pga把命中率提高到90以上就可以 了

2楼

2021-01-27 11:47

短期解决方法:

open_cursors = 600调高.这个不影响Oracle的其他性能.

长期解决方法:

open_cursors = 600调高

打Oracle补丁集到817.

3楼

2021-01-27 10:09

ORA-00600的错误很多时候是oracle的bug造成的，816有个bug号是770924，会造成这个问题，已经在8161版本修复了。你可以尝试下升级Oracle。

查了一下资料，据说cursor_space_for_time这个参数改成FALSE也可以，没有尝试过。试试看吧？

4楼

2021-01-27 08:58

TROUBLESHOOTING STEPS

For any ONE-TIME occurrence we can safely ignore the error. This error does not cause to any potential data corruption or any data loss. Check Note 35928.1 for known issues and two basic usages of OERI(12333):

Usage with 3 additional numeric values

Usage with 4 additional values ... new since 8.0.X

In case the errors are seen consistently and no known issues matches to your issue then do the following

Common Causes & Solutions:

1. Check the client software version. An incompatible client software is a common cause of this error. Upgrade the client software to current version (i.e. match the server version).

The following note explains the supported combinations of clients for a particular RDBMS Server release.

Note 207303.1 Client / Server / Interoperability Support Between Different Oracle Versions

Similar issues are reported when the client installation is faulty.

2. An incompatible NLS Client setting can also trigger such internal errors. Check the NLS settings as explained in the following note.

Note 77442.1 ORA_NLS (ORA_NLS32, ORA_NLS33, ORA_NLS10) Environment Variables explained

3. There are a number of bugs associated with the use of bind peeking. Turn off bind peeking as follows:

alter system set "_optim_peek_user_binds"=false;

4. Please review your listener.log and SQLNET log for network errors at the time of the 1233 errors. Correct these errors.

Try to reproduce the issue from a different client machine, preferably from server. This will rule out the possibility of bad network. If the execution fails from a particular client then it could be due to the bad network from that client to server. The error ORA-600[12333] could occur when a request is being received from a network packet and the request code in the packet is not recognized.

5. Ask your sysadmin to correct any network delays. A slow network can lead to this error.

6. If the error still continues , then do the following to understand from where the error is generated.

We need to understand which session/program/application that triggers this issue. This shall be found from the trace files under the session state object '(session)'. Sometimes the ORA-00600 [12333] trace files will not capture the session information. In such cases we can check with the end users about any issues around the time-frame of this internal error.

There is a HIGH chance for application run-time exception to lead to this ORA-00600 [12333]. Due to the unhandled exceptions there is a chance for incomplete information passed to the server hence the internal errors are raised. In such cases, handling those exceptions (or) addressing those errors on the application code will resolve the issue.

In few cases, the problem application will work for a while before it terminates with the error. This could be due to the TIMEOUT settings at the Application Server (or) Forms Server.,etc. To resolve this either tune the failing application to complete within the TIMEOUT value (or) reset the TIMEOUT to an optimal value.

There could be more possibilities here; in simple words the approach should be from application side, which would help us to understand the other issues that triggered this network interruption (ORA-00600 [12333]).

Check the 'Current SQL Statement' section of the incident trace files. Does each trace file point to the same SQL statement. If so, there may be a problem with the code.

7. If you notice JDBC Client as the failing program under Session state object, please check the following

That you use latest compatible version of JDBC Drivers in your application side.

Note 430839.1 to verify the version of JDBC Drivers and for Installation steps.

Monitor and try to handle correctly the timeouts from the application

Check that idle or died programs/processes are not just killed at the client side but using a good cleaning procedure.

Increase queue sizes / buffers and similar from the jdbc side.

Further diagnostics regarding JDBC Application driver can be found:

Note 1361107.1 Suggestions For Troubleshooting ORA-3137 [12333] Errors Encountered When Using Oracle JDBC Driver

8. In-case if all the above suggestions does not help to identify the cause, and the ORA-00600 [12333] persists we may need to enable the networking tracings from the problem client and need to review the network traces to understand where the problem occurs. See Note 219968.1 Title: SQL*Net, Net8, Oracle Net Services - Tracing and Logging at a Glance. Check the network logs for errors and fix them with the network administrator.

E.g.:

12333错要 具体诊断的

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!

诗檀软件专业数据库修复团队

我要举报

如果感觉以上信息为低俗/不良/侵权的信息，可以点下面链接进行举报，我们会做出相应处理，感谢你的支持！

点此我要举报以上信息！

推荐资讯

大家都在看