In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-02 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)05/31 Report--
This article mainly shows you "how to do ORA-600 error in oracle", the content is simple and easy to understand, organized clearly, I hope to help you solve doubts, let Xiaobian lead you to study and learn "how to do ORA-600 error in oracle" this article.
ORA-00600:internal error code, arguments: [4194], [43], [46], [], [], [], [], []
Most of this happens because of unexpected downtime and errors reported during startup. DB cannot start.
Method 1: Using system segments
(1) Create pfile with spfile, and then modify parameters:
#.undo_tablespace='UNDOTBS1'
#.undo_management='AUTO'
#.undo_tablespace
#.undo_retention
undo_management='MANUAL'
rollback_segments='SYSTEM'
(2) Restart DB with modified pfile
SQL> STARTUP pfile='F:/initorcl.ora' ;
(3) Delete the original tablespace and create a new UNDO tablespace
SQL> drop tablespace undotbs;
SQL> create undo tablespace undotbs1 datafile '/u01/oradata/undotbs1.dbf' size 10M;
(4) Close the database, modify the pfile parameter, and then create spfile with the new pfile, and start the database normally.
.undo_tablespace='UNDOTBS1'
.undo_management='AUTO'
#undo_management='MANUAL'
#rollback_segments='SYSTEM'
Method 2: Skip the damaged segment
In method 1, we use system segments. From the first part we learned that there are multiple undo segments, we can use the alert log to see which segments are in use, these segments may be damaged. We just need to skip these broken segments, start DB normally first, create a new UNDO table space, and switch.
(1) Modify pfile and add parameters:
*._ corrupted_rollback_segments='_SYSSMU11$','_SYSSMU12$','_SYSSMU13$'
The values of these fields are checked through the alert log. It can also be viewed with the following command:
#strings system01.dbf | grep _SYSSMU | cut -d $ -f 1 | sort -u
(2) Start DB with modified pfile
DB can start normally because of the broken segments skipped.
(3) Create a new UNDO table space and switch over
SQL> create undo tablespace undotbs1 datafile '/u01/oradata/undotbs1.dbf' size 10M;
SQL> alter system set undo_tablespace=undotbs1;
SQL> drop tablespace undotbs;
(4) Modify pfile, create spfile, and start normally
Delete:
*._ corrupted_rollback_segments='_SYSSMU11$','_SYSSMU12$','_SYSSMU13$'
The above is "oracle ORA-600 error how to do" all the content of this article, thank you for reading! I believe that everyone has a certain understanding, hope to share the content to help everyone, if you still want to learn more knowledge, welcome to pay attention to the industry information channel!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.