PLS-00172: string literal too long
今天寫一個表的整合儲存過程,由於這個表的欄位比較多,達到了762個欄位,加上最後一個插入操作是要對所有的欄位進行nvl(column_name,0)的操作,編譯之後報錯如下:
Compilation errors for PROCEDURE orcl.PR_CUST_CONSUME
Error: PLS-00172: string literal too long
Line: 208
Text: EXECUTE IMMEDIATE '
網上查詢了相關的資料發現如下解釋
Cause: The string literal was longer
than 32767 bytes.
Action: Use a string literal of at most
32767 bytes.
將報錯的那一段放入一個文字檔案中 檢視屬性:
34,967 位元組
超過了之多32767的限制.
沒有辦法只能分批對欄位進行nvl的轉換了 修改之後 32,056位元組 沒有超過限制,執行編譯:
compiled successfully
將修改前的程式碼放入word ,工具-字數統計:34508個字元,13頁
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/12216142/viewspace-503387/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-01704: string literal too long 與CLOB
- ORA-01489: result of string concatenation is too long
- WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!AIENQ
- 0403-027 The parameter list is too long for AIXAI
- Error format not a string literal and no format arguments解決方案ErrorORM
- 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
- ORA-01861: literal does not match format stringORM
- 一次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
- File name too long window和linux排查,解決Linux
- Error running ‘Application’Command line is too longErrorAPP
- SyntaxError: EOL while scanning string literal錯誤解決ErrorWhile
- 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的解決辦法
- Specified key was too long; max key length is 1000 bytes
- 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
- SAP:CX_SY_READ_SRC_LINE_TOO_LONG解決
- 解決 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
- SP2-00027: Input is too long (> 2499 characters) - line ignored
- 執行遷移檔案報錯 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
- [Javascript] template literal tagJavaScript