Oracle数据迁移Shell脚本出现Unexpected End Of File Error报错

Hey there, let's tackle this frustrating error you're hitting in your production-to-test Oracle data migration script. Since it worked fine before you added new logic, the issue is almost certainly tied to syntax mistakes introduced in your recent changes. Here’s a breakdown of the most common culprits and how to fix them:

Common Causes & Fixes #

1. Unclosed Conditionals or Loops #

Shell scripts are strict about matching opening/closing keywords for control structures. If you added an if, while, or for block but forgot the corresponding fi, done, or esac, the shell will reach the end of the file still looking for the closing marker—triggering the "Unexpected End Of File" error.

Example of a broken block:

# Check if Production ETL is complete
if [ "$PROD_ETL_STATUS" = "COMPLETE" ]
then
    echo "Production data is ready for migration"
    # New logic added here... but no closing fi!

Fix: Double-check every new control structure you added. Make sure every if has a matching fi, every while/for has a done, and every case has an esac.

2. Unclosed Quotes or Backticks #

Forgot to close a single quote ('), double quote ("), or backtick (`)? The shell will keep scanning the rest of the script looking for the closing character, right up to the end of the file. This is super easy to miss when adding new SQL calls or variable assignments.

Example of a broken quote:

# Check Test DB update status
TEST_LAST_UPDATE=$(sqlplus -s $TEST_CREDS <<EOF
SELECT MAX(update_timestamp) FROM test_migration_log WHERE environment = 'TEST
EOF

Notice the unclosed single quote in the SQL WHERE clause? That’s a guaranteed EOF error.

Fix: Scan your new code for any quoted strings or command substitutions. Use syntax-highlighting in your editor—most will highlight mismatched quotes visually.

3. Heredoc Syntax Mistakes #

Since you’re working with Oracle, your script almost certainly uses heredocs (<<EOF) to pass SQL to sqlplus. The number one mistake here is indenting the closing EOF marker. It must be on its own line, with no leading spaces, tabs, or other characters.

Example of a broken heredoc:

sqlplus -s $PROD_CREDS <<EOF
SELECT etl_complete_flag FROM prod_etl_control;
    EOF  # Leading tabs here break the heredoc!

The shell won’t recognize the indented EOF as the end of the heredoc, so it’ll keep reading until the file ends.

Fix: Ensure your heredoc closing marker is left-aligned, with nothing before or after it on the line (not even a space).

4. DOS Line Endings #

If you edited the script on Windows and transferred it to Linux/Unix, it might have DOS-style line endings (\r\n) instead of Unix-style (\n). The shell interprets the \r as part of the line, which can break keywords like fi or done—leading to unexpected EOF errors.

How to check: Run cat -A your_script.sh—look for ^M at the end of lines (that’s the \r character).

Fix: Convert the script to Unix line endings with dos2unix your_script.sh.

Quick Debugging Tips #

• Run bash -n your_script.sh to perform a syntax check without executing the script. This will point you directly to the line number where the syntax breaks.
• Comment out the new logic you added, then re-run the script. If it works again, uncomment sections one by one to isolate the problematic code.

内容的提问来源于stack exchange，提问作者need_java