Error In Executing Triggers In Database Startup
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in General Database Discussions All PlacesDatabaseGeneral Database Discussions This discussion is archived 6 Replies Latest reply on Dec 12, 2005 5:08 PM by 274340 Database startup error message 274340 Dec 9, 2005 9:07 PM Hi Guys, When I startup my Database, I always see this error message printed in the trace file: Error in executing triggers on database startup *** 2005-12-09 11:12:42.817 ksedmp: internal or fatal error ORA-00604: error occurred at recursive SQL level 1 ORA-12663: Services required by client not available on the server ORA-36961: Oracle OLAP is not available. ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1 ORA-06512: at line 15 Error in executing triggers on database startup *** 2005-12-09 11:12:42.869 ksedmp: internal or fatal error ORA-00604: error occurred at recursive SQL level 1 ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06512: at line 4 I have a few questions about the above message: 1. How can I see which database startup trigger is having this error? Is there a way to determine that? 2. Is there a way I can disable all triggers that fire on database startup? (just like we can disable triggers on a table) 3. Any idea what ORA-36961: Oracle OLAP is not available. means? Thanks 12260Views Tags: none (add) This content has been marked as final. Show 6 replies 1. Re: Database startup error message 176447 Dec 9, 2005 9:22 PM (in response to 274340) You may check the dba_triggers - trigger_body for the similar contents in the error message. You also look for triggering_event for identifying startup triggers. Yes. You can disable the trigger. OLAP is an opt
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > ORA-00604 error while opening the database Want to Advertise Here? Solved ORA-00604 error while opening the database Posted on 2004-10-13 Oracle Database 2 Verified Solutions 15 Comments 11,144 Views Last Modified: 2011-08-18 Hi, When i try to start a database, system throws the ORA-00604 error but still it opens the database and iam able to work on that database only for few minutes , after that the iam getting the following message ORA-12500: TNS:listener failed to https://community.oracle.com/thread/348778 start a dedicated server process and when i checked the alert log and trace file, it shows ORA-00604 error. Find below the contents of alert log and the trace file. Server process System parameters with non-default values: processes = 59 shared_pool_size = 262144000 large_pool_size = 614400 control_files = e:\ORANEW\oradata\FCIS45\control01.ctl, e:\ORANEW\oradata\FCIS45\control02.ctl, e:\ORANEW\oradata\FCIS45\control03.ctl db_block_buffers = 25600 db_block_size https://www.experts-exchange.com/questions/21166274/ORA-00604-error-while-opening-the-database.html = 8192 compatible = 8.1.0 log_buffer = 10485760 log_checkpoint_interval = 10000 log_checkpoint_timeout = 1800 db_files = 1024 db_file_multiblock_read_count= 8 rollback_segments = RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6 max_enabled_roles = 30 remote_login_passwordfile= EXCLUSIVE global_names = FALSE distributed_transactions = 10 instance_name = FCIS45 service_names = FCIS45 open_links = 4 sort_area_size = 1048576 sort_area_retained_size = 65536 db_name = FCIS45 open_cursors = 100 os_authent_prefix = optimizer_mode = RULE job_queue_processes = 4 job_queue_interval = 60 parallel_max_servers = 5 background_dump_dest = e:\ORANEW\admin\FCIS45\bdump user_dump_dest = e:\ORANEW\admin\FCIS45\udump max_dump_file_size = 10240 oracle_trace_collection_name= PMON started with pid=2 DBW0 started with pid=3 LGWR started with pid=4 CKPT started with pid=5 SMON started with pid=6 RECO started with pid=7 SNP0 started with pid=8 SNP1 started with pid=9 SNP2 started with pid=10 SNP3 started with pid=11 Wed Oct 13 12:19:51 2004 alter database moun
is not pinning all packages From: