Export DDL Button is grayed out

Dear Toad Experts, I need to export a DDL script of all users on the database. I
went to Export -> Export DDL -> Script Options. Unfortunately, the “Export DDL”
execution button is grayed out which means the Export DDL option has been
disabled. Do I have to have a special license to turn it on? I have the license
of Toad For Oracle Xpert (my toad is on Version 10.6.1.3), but don’t have the
Toad DBA Module. Thank you in adance,

Lisa

If you open that window from the main menu, you have to add objects into it with
the ‘add’ button.

It is much easier to go to the Schema Browser, select the objects that you are
interested in (CTRL+A to select all), then rt-click and choose “Create
Script”. Then the Export DDL window will open pre-loaded with your
selected objects.

Have you actually populated the Objects and Output tab with your users? The
green “run” button does not become enabled until you have something
to export
image001.jpeg

Have you actually populated the Objects and Output tab with your users? The
green “run” button does not become enabled until you have something
to export
image001.jpeg

Thank you so much for all tips. The “Create Script” won’t export the password
while the “Export DDL” will export password. I need to move all users on DEV DB
to TEST DB without resetting up the passwords.
Cheers,

Lisa

Matt,

You are absolutely right. After I added data in the Output tab, the button is
green now. I ran it and got a script. Unfortunately, the password in the script
is “” which is not I am looking for. I remember that I used the
early version of Toad to export the user with the encrypted password, then I
used the script to run on other DB. Could you shed some light on how to get
encrypted password with user create script via Toad?

Any help , will be greatly appreciated.

Lisa

In the export DDL dialog, on Script Options -> Users, make sure “if possible,
include ‘identified by values’ clause in 11g” is checked.

This will only work if you have select privileges on the SYS.USER$ table.

It’s about the version of Oracle as much as the version of Toad.

Oracle used to put the encrypted passwords in DBA_USERS, but for Oracle 11, they
stopped doing that, and the encrypted passwords are only in SYS.USER$. Maybe
this is another option that could be removed, and we should always just look in
SYS.USER$ if the user has privileges.

When Toad is connected to 10g and older, the encrypted password still comes out
of Toad without checking any options.

-John