Unable to export schema fue to ORA 00092 get schema size info

Posted on 2011-03-21
Medium Priority
Last Modified: 2012-05-11
Hello Experts,

I am trying to export a DB schema but I am receiving ORA 00942 "get schema size info".

I need to backup a copy of a schema before reinstalling the HW. I have performed a cold backup but would still like to have a schema export done.

Google gives some ambigous explanation for this error and very little help on the steps to actually fix it.

Any help will be appreciated.


Question by:FABRICIO76
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 15

Expert Comment

by:Aaron Shilo
ID: 35180381

you LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC

check the size of the  LARGE_POOL_MIN_ALLOC and set the  LARGE_POOL_SIZE
toa higher value.

Author Comment

ID: 35180402
Hello Ashilo,

I am increasing the memory setting and testing immediately.



Author Comment

ID: 35180454
Hello Ashilo,

We are still seeing the same error, even after increasing the memory from a small sized template to a large.

Any further ideas?

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

LVL 15

Assisted Solution

by:Aaron Shilo
Aaron Shilo earned 668 total points
ID: 35181127

the error you display in the screenshot is an error
regarding the actual exsistance of the table .

1. are you using the owner of the table ?
2. use fully qualified names schemaname.objectname
3. make sure you have privileges to access the table.
LVL 48

Assisted Solution

schwertner earned 664 total points
ID: 35183656
This means that the schema or the table doesn't exist in the database.
As mentioned over this could be typo, lack of privilige to access the schema/table, or even wrong database.

Accepted Solution

gopisera earned 668 total points
ID: 35185877
Yeah, Hoping this problem exists due to the privilege issue mainly.

Or run as an root user and check.

Author Closing Comment

ID: 35187457
Hello Experts,

Thank you for your help.

Indeed it was lack of privileges, I applied the following scripts and re tested succesfully.

I am splitting the points since all pin pointed that this could be privileges.

grant exp_full_database to myuser;
grant imp_full_database to myuser;

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Truncate is a DDL Command where as Delete is a DML Command. Both will delete data from table, but what is the difference between these below statements truncate table <table_name> ?? delete from <table_name> ?? The first command cannot be …
From implementing a password expiration date, to datatype conversions and file export options, these are some useful settings I've found in Jasper Server.
This video shows syntax for various backup options while discussing how the different basic backup types work.  It explains how to take full backups, incremental level 0 backups, incremental level 1 backups in both differential and cumulative mode a…
Via a live example, show how to take different types of Oracle backups using RMAN.

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question