855927 wrote:That's part of the story. What's the bigger picture? Are you generating INSERT statements in database A, so that you can replicate the data in database B? There are lots of ways to do that without generating INSERT statements. Database links, data pump (or the older exp and imp utilities) come to mind right away.
The story is like this.
I have a bunch of insert statement. and currently doing @importable1.sql AT sqlplusHow are these INSERT statements being created?
importable1.sqlWhat exactly happens? Can you post a test script that people can run and re-create the problem?
INSERT INTO T_CIMS_TEMPLATE (ID, INFO) Values (1, 'SOME VERY LONG STRING THAT MAKES ..................THIS LINE MORE THAN 2500 LENGTH' );
I have done some research.
Some of the suggestion 4 solutions are
1. Break the line manually to become <2500
INSERT INTO T_CIMS_TEMPLATE (ID, INFO) [break the line at here]
Values (1, 'SOME VERY LONG STRING THAT MAKES ..................THIS LINE MORE THAN 2500 LENGTH' );
2. Use SQL*Loader
3. insert T_CIMS_TEMPLATE values ('string < 2000 chars' ||
'another piece of the string ' ||
4. Insert into T_CIMS_TEMPLATE... then UPDATE t_CIMS_TEMPLATE
5. Use SQL developer to execute the importable1.sql
Problem is must i have a lot of insert script and it cause too much man power to do a manual job.
I have tried SQL Developer 3. It hangs on large tables.
Is there an alternative ( beside sqlplus ) to overcome this limitation of 2500 lines?Is the threshold 2500 lines , or 2500 characters on a single line?