Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
faq:migration-toolkit:load-parameterization [2019/06/13 18:00] 127.0.0.1 external edit |
faq:migration-toolkit:load-parameterization [2019/07/25 10:29] darya.prikhodkina |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== How to Parameterize Login Information After Import Script Generation ====== | + | ====== How to Parameterize Login Information After Generation of Import Script ====== |
- | You can use environment variables to specify the **SERVISE**, **PASSWORD** and **USER** for the whole run in //**sqlways_all.bat**//. But first you need to specify those environment variables in the SQLWays, so that it used them in all the bat files with the commands, like: | + | You can use environment variables to specify the **SERVISE**, **PASSWORD** and **USER** for the whole run in //**sqlways_all.bat**//. But firstly you need to specify these environment variables in SQLWays Wizard, so that it could them in all the bat files with the commands, like: |
{{:faq:migration-toolkit/load-parameterization.png|}} | {{:faq:migration-toolkit/load-parameterization.png|}} | ||
Line 7: | Line 7: | ||
The Password is specified as **%PASSWORD%** here. | The Password is specified as **%PASSWORD%** here. | ||
- | So, as the result you will have bat files for data and ddl loading with the commands like, e.g. for Oracle: | + | As the result you will have bat files for data and ddl loading with the commands like, e.g. for Oracle: |
sqlplus %USER%/%PASSWORD%@%SERVICE% @calendar_ddl.sql | sqlplus %USER%/%PASSWORD%@%SERVICE% @calendar_ddl.sql | ||
- | All the bat files are run using the //**sqlways_all.bat**// file with the command like: | + | All the bat files are ran using the //**sqlways_all.bat**// file with the command like: |
sqlways_imp.exe /bat=sqlways_all.bat | sqlways_imp.exe /bat=sqlways_all.bat | ||
- | So, all that is left to do is to update the //**sqlways_all.bat**// file with the following **SET** commands before the **CALL** statements: | + | So all that is left is to update the //**sqlways_all.bat**// file with the following **SET** commands before the **CALL** statements: |
set USER=ora | set USER=ora | ||
set PASSWORD=pass | set PASSWORD=pass | ||
Line 21: | Line 21: | ||
sqlplus ora/pass@ora @calendar_ddl.sql | sqlplus ora/pass@ora @calendar_ddl.sql | ||
- | So, changing just three values in the sqlways_all.bat file, you can control which user, password and service name must be used for the whole load. | + | As you can see, by changing just three values in the sqlways_all.bat file, you can control which user, password and service name is to be used for the whole load. |
\\ | \\ |