Schema export problems/questions

Toad for Oracle & DevOps Toolkit
1

Hello John,

I’ve some problems with schema export function in the latest GA (2026.R1) version.

  1. I checked Scheduler under Extract/Types but none of the defined scheduler jobs exported during the process. I tried to select only “Scheduler/Jobs” but it didn’t help also.
  2. There is a checkbox under Settings|Other Objects|Triggers to control how to handle schema names in triggers. I don't want a schema name in my extracted script, so I unchecked that, and also unchecked the "Include schema name" option under Settings|Script. This caused Toad to generate the source code for the triggers with the object names enclosed in "". So when I compared the exported schema library with the corresponding svn source code for the schema, I got a lot of differences under the /Triggers directory - but the only difference is in the first line of code, which is the use of "". Is there a way to make TOAD ignore the use of "" characters during schema export?

thanks

Tamas

2

Hi Tamas,

I just tried Generate Schema Script in version 2026 R1.

  1. The scheduler jobs exported just fine for me - so sorry to ask dumb questions, but...
    a) Are you sure you are in the right schema?
    b) Do you have a filter set here?

    image
    image1013×757 44.2 KB

  2. Options -> Other Objects -> "Parse triggers for schema names", if unchecked, will export trigger source exactly as it appears in the database. Maybe it has a schema name in there, maybe it doesn't. It depends on the script that created the trigger. Checking that box means "add or remove it according to the overall "include/exclude schema option". Unchecking that box means "just export it as-is".

So If you want to be sure to not have schema name in your script:
a) CHECK Options -> Other Objects -> Parse triggers for schema names
b) UNCHECK Options -> Script -> Include Schema Name before object name.

3

  1. I'm sure the settings were correct and selecting SB |Scheduler Jobs gave 11 records. Today I ran a schema export again on the desired schema and for the first time Toad also exported the scheduler tasks correctly. However, after changing the settings today I managed to reproduce the case where the Scheduler jobs were not exported (see attached images).

    Could the possible malfunction be caused by "Jobs" or "Mat Views" being unchecked? Even though I switched the above options back, the scheduler jobs are still not included in the export package.

    image
    image1057×324 22.2 KB

image
image1210×539 44.2 KB

image
image644×251 3.84 KB

image
image380×355 12.6 KB

  1. I understand how it is possible to remove "burned in" schema names from the source code of triggers when they were compiled into the database in this way. My problem, however, is that Toad puts the trigger name between " " characters when I use the options you provided. My question was, can the schema export generate source code without " " signs, and if so, how can it be done?
4

  1. I just ran generate schema script, scheduler items only, and it worked as expected. Then I set my filter and object selections like yours and it still worked. So I'm not sure why it doesn't work for you. Settings for Jobs or MViews should not be relevant. Try turning on Spool SQL and see if you get any clues in there. Feel free to post the output, or send it to me if you want.

  2. Trigger names don't become quoted when I do that. I even had a few that were in lower case in my source code and they remained unquoted. What setting do you have in Options -> Oracle -> General -> Double Quote Object names? The default setting is "non-ascii", and that's what I have it set to. I think "All" would make them quoted but I doubt that's what's happening here.

Do the trigger names have double-quotes in DBA_SOURCE?

5

To the schema export would you please try the following situations one after the others?

1.) export schema with every options I’ve checked (Scheduler Jobs exported successfully)

2.) then enable only jobs under Scheduler groups (in this time Scheduler Jobs also exported successfully

3.) re-enable the whole Scheduler group with its corresponding checkbox, it seems in this situation every Scheduler object types should export in the output (but this time Scheduler Jobs are missing from my export pack)

Thanks

6

Ah! Yes, I can reproduce the problem when I do it that way. Once that starts happening, the only way I can seem to fix it is to close and re-open generate schema script, then check "Scheduler" again if necessary.

Thanks. I'll see what's going on there and fix. I wonder if that happens for some of the other checkboxes with sub-check boxes.

1 Like
7

Yes, the data of DESCRIPTION under user_triggers contains the following data: "schema name"."trigger name". I have checked “Parse triggers for schema names” value, and unchecked “Include schema names before objects name” value during export – that could be the reason I get the source code of triggers where object names surrounded by apostrophe.

I was wondering if there is a way to remove “ characters around the object names in the generated code. But I think the correct answer in this case will be no.

Anyway, “double quotes object names” value is set to the default value.

8

If source code is present for the trigger in USER_SOURCE, we will use that instead of USER_TRIGGERS. But I think you will find double-quotes consistent between both of them.

There is no way to have Toad remove the double-quotes other than just manual search/replace, sorry.