Idea:Processor for "imp show=y" log file.
Why?
The problem is, how to keep database small when importing with rows=n parameter, because when database consists form large amount of tables and indexes, quite small initial extent can make empty database pretty big.
Guru says: Make database structures with small initial extent than do imp with ignore=y.
But how to make scripts for existing structures?
They saying: use imp with show=y parameter, and get all statements from log file.
Cool imp is fast, but huge log file is very unhandy because of its format. I can't find any separator for DDLs
and changeing it by hand is hopeless. 
So i see another feature for our great PL/SQL Devloper
, the processor for "imp show=y" log file.
It can be used by DBAs and programmers to make create database objects scripts from existing database.
And exp is the tool you can trust it produce the good DDL statements.
What do You think?
PS: Is there other way to change initial extents while importing? Excluding phisical change of .dmp file replacing too big initial extents.
Why?
The problem is, how to keep database small when importing with rows=n parameter, because when database consists form large amount of tables and indexes, quite small initial extent can make empty database pretty big.
Guru says: Make database structures with small initial extent than do imp with ignore=y.
But how to make scripts for existing structures?
They saying: use imp with show=y parameter, and get all statements from log file.
Cool imp is fast, but huge log file is very unhandy because of its format. I can't find any separator for DDLs


So i see another feature for our great PL/SQL Devloper

It can be used by DBAs and programmers to make create database objects scripts from existing database.
And exp is the tool you can trust it produce the good DDL statements.
What do You think?

PS: Is there other way to change initial extents while importing? Excluding phisical change of .dmp file replacing too big initial extents.