Database Administration (MOSC)

MOSC Banner

How to fix ORA-22813

edited Jul 11, 2019 5:02AM in Database Administration (MOSC) 6 commentsAnswered

Hi!

A customer has come across this in one project, that is quite big. I don't quite understand this 30K limitation I am suddenly reading about for queries (some sort of queries?). Can't we trust that a system we have running for lot's of customers is stable, because any sql could run into a limitation if a database suddenly has too many objects of one kind or another? How can we secure against this?

But most important: Is there no way to set some parameter in Oracle to increase this limit (I found "ALTER SYSTEM SET EVENT = '44410 trace name context forever' scope=spfile;", but that works only for queries with xmlagg, I think?)? We can't suddenly fix the sql itself, this is a part of a large system, we would have to make an update of our program and send it out. But the customer is stuck NOW.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center