Question2Replies817Views RaymondK2522 Member since 2017 3 posts Virgin Media Ireland Limited Posted: 2 years agoLast activity: 2 years 5 months ago Closed Issue with the script generated from the View/Download SQL DDL option when importing products via the Import WizardI have been importing a number of products into a new environment setup of Pega 7.31. It is using a split schema and we are unable to apply the schema changes automatically.I downloaded the SQL DDL script and executed it on the database using sqlplus.However the output from the execution had a number of errors and a large number of lines ignored.The majority errors and ignores were the creation of Indexes, but there were some Alter table statements throwing errors too.The problem seems to be the script that is generated, all of the Indexes had extra newline characters between the column names and also between the closing bracket and the closing semicolon; This means i have to manually go through each generated script and validate the statements, adding additional time to the environment creation. I am not sure if executing the scripts using another tool will help as all I have access to is sqlplus on a linux server that can connect to the database.Is there any other options that i have here, or is there some other way I can generate the script that will remove these extra characters Pega Customer Service Low-Code App Development Installation and Deployment Data Integration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 2 years agoSantanu PEGA replied to RaymondK2522Which version to which version you are upgrading? Also is there any change in DB? Posted: 2 years agoRaymondK2522 Virgin Media Ireland Limited replied to SantanuWe were not Upgrading it was a new install of 7.31. Yes there is a change in the DB, the generated scripts contain CREATE statements and ALTER statements. The extra spaces were only noticed with the CREATE INDEX statements. A support ticket was created And the following advice was given: To check the article ORA-00921 when applying schema SQL on Oracle (SA-49717) for help Do not encounter the issue when running the import script through a UI based tool such as SQLDeveloper You should be able to get this to run though SQLPlus as well, by specifying the following setting before attempting to run the SQL file: - set sqlblanklines on PL/SQL statements that contain blank lines will still run through SQLPlus without causing errors. A enhancement request was raised, FDBK-24201, to ask for the SQL generation to remove blank lines (unless they are within a PL/SQL block).