ORA-08412: error encountered in WMSGBSIZ, size for WMSGBLK
is not big enough for warning message
- 1 Answers
- 2806 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: The WMSGBSIZ is the maximun size for warning message
block, it is recommanded to be 1024 bytes to 8 kbytes.
Action: Defined WMSGBLK of size between 1k to 8k bytes and
update the WMSGBSIZ to the sizeof(WMSGBLK).
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
NZE-28890: Entrust Login Failed
ORA-16627: No standby databases support the overall protection mode.
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-26032: index string.string loading aborted after string keys
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
RMAN-05017: no copy of datafile number found to recover
ORA-26084: direct path context already finished
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
ORA-26027: unique index string.string partition string initially in unusable state
NZE-28868: Peer certificate chain check failed.
ORA-16516: The current state is invalid for the attempted operation.
ORA-26030: index string.string had string partitions made unusable due to:
ORA-26028: index string.string initially in unusable state
