SP2-00027: Input is too long (> 2499 characters) - line ignored
參考Metalink: Doc ID: Note:115005.1 [@more@]SP2-00027: Input is too long (> 2499 characters) - line ignored
Problem Description
-------------------
You are trying to run a SQL query or script from an output file from a vendor
package called SQLBacktrack. The file has a SQL statement that is extremely
long (in this case thousands of lines long and each row has thousands of
characters) and you get the following error:
SP2-0027: input is too long (> 2499 characters) - line ignored
This fails with the same error from either SQL*Plus or Server Manager.
Solution Description
--------------------
Open the file in a text editor and then resave the file as a different file
type. In Microsoft Word, you click on File, Save As, then select file type
'text only with line breaks' and save the file. Once this is done, you can
successfully run the script from SQL*Plus or Server Manager.
Explanation
-----------
The output file that comes directly from SQLBacktrack doesnot have the proper
type of carriage returns that SQL*Plus or Server Manager recognizes. As a
result, the SQL statement is read by SQL*Plus or Server Manager as being all on
one line and you get the above error message. Once you save the file as 'text
only with line breaks' it reformats the carriage returns in the file so that
SQL*Plus or Server Manager can recognize it and run the statement successfully.
Additional Search Words
-----------------------
SQLBackTrack sp2-27
Problem Description
-------------------
You are trying to run a SQL query or script from an output file from a vendor
package called SQLBacktrack. The file has a SQL statement that is extremely
long (in this case thousands of lines long and each row has thousands of
characters) and you get the following error:
SP2-0027: input is too long (> 2499 characters) - line ignored
This fails with the same error from either SQL*Plus or Server Manager.
Solution Description
--------------------
Open the file in a text editor and then resave the file as a different file
type. In Microsoft Word, you click on File, Save As, then select file type
'text only with line breaks' and save the file. Once this is done, you can
successfully run the script from SQL*Plus or Server Manager.
Explanation
-----------
The output file that comes directly from SQLBacktrack doesnot have the proper
type of carriage returns that SQL*Plus or Server Manager recognizes. As a
result, the SQL statement is read by SQL*Plus or Server Manager as being all on
one line and you get the above error message. Once you save the file as 'text
only with line breaks' it reformats the carriage returns in the file so that
SQL*Plus or Server Manager can recognize it and run the statement successfully.
Additional Search Words
-----------------------
SQLBackTrack sp2-27
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/7318139/viewspace-926753/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- [20210113]SP2-0232 Input too long. Must be less than 241 characters.txt
- Command line is too long. Shorten command line for JooLunMallApiApplication or also for Spring Boot default configuration?APIAPPSpring Boot
- WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!AIENQ
- PLS-00172: string literal too long
- 0403-027 The parameter list is too long for AIXAI
- idea遇見Command line is too long. Shorten command line for Main or also for Application default configuration?IdeaAIAPP
- IntelliJ IDEA 執行專案的時候提示 Command line is too long 錯誤IntelliJIdea
- IDEA命令列縮短器助你解決此問題:Command line is too long. Shorten command line...Idea命令列
- Spring Boot Intellij 執行應用的時候 Command line is too long. Shorten command line for 錯誤Spring BootIntelliJ
- Laravel 5.4 常見錯誤:Specified key was too longLaravel
- 故障排除:"WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! "AIENQ
- WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!的分析AIENQ
- 一次WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCKAIENQ
- MySQL:Specified key was too long; max key length is 767 bytesMySql
- 【故障處理】-0403-027 The parameter list is too long
- ORA-01704: string literal too long 與CLOB
- File name too long window和linux排查,解決Linux
- Laravel 5.5 資料遷移問題:Specified key was too longLaravel
- 【MOS】Index Rebuild Is Hanging Or Taking Too Long (文件 ID 272762.1)IndexRebuild
- Metlink:Troubleshooting:WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!AIENQ
- ORA-00494 enqueue [CF] held for too long故障分析處理ENQ
- -bash: /bin/rm: Argument list too long的解決辦法
- mysql specified key was too long與Index column size too large. The maximum column size is 767 bytes.MySqlIndex
- 刪除大量檔案Argument list too long錯誤解決
- ORA-00494: enqueue [CF] held for too long (more than 900 seconds)ENQ
- WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! 與 dc_tablespcesAIENQ
- 通過system state dump分析WAITED TOO LONG FOR A ROW CACHE ENQUEUEAIENQ
- WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK-[ID 278316.1]AIENQ
- git拉取程式碼報錯filename too long unable to create fileGit
- 解決 Specified key was too long ... 767 bytes 的本質問題
- ORA-00494: enqueue [CF] held for too long (more than 900 seconds) -RACENQ
- 翻譯metalink關於WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK文章AIENQ
- 執行遷移檔案報錯 1071 Specified key was too long.
- idea在使用git clone 時出現Filename too long的報錯資訊IdeaGit
- ora-12169 tns net service name given as connect identifier is too longIDE
- Excel為批註設定圖片背景 出現Bad Request - Request Too longExcel
- 【k8s】etcd叢集took too long to execute慢日誌告警問題分析K8S
- 偶遇ERROR 1071 (42000): Specified key was too long; max key length is 767 bytesError