May 6, 2014 Leave a comment
So many times we stuck into situation where we were helpless to start database instance using simple oracle text initialization file for auxiliary instance or some test instance. Usually this is very common whenever we copy the sample or source parameter file from some html or formatted document editor, which allow Unicode text. Frustrating thing is that even after checking test file on normal vi editor or notepad couple of time will also not allow to get rid of that mess-up in parameter file. In this situation there are multiple ways to fix the issue.
- Copy the content into notepad and then copy back to the unix console to see if it help. Focus on special characters like ‘, ‘ , “,” etc . Autosuggest options of smart word editors usually convert actual characters into these formatted charters. As soon as you copy the full parameter file content in to notepad or any other low end text editor it’s not that difficult to manually correct it until unless the size of configuration file is large.
- Other way is to use od (Octal Dump), a very old utility of unix OS.
Today we will demonstrate the troubleshooting of junc character by using od as well as conventional method.
Here we have created two text parameter files and one with ‘ ‘ instead of ‘ ‘
[firstname.lastname@example.org] ls -lrt initMASK*
-rw-r–r– 1 oracle oinstall 912 May 6 16:46 initMASK11G.ora_correct
-rw-r–r– 1 oracle oinstall 916 May 6 16:54 initMASK11G.ora
[email@example.com] diff initMASK11G.ora_correct initMASK11G.ora
Let’s try to start instance using this corrupted parameter file.
SQL> startup nomount pfile=’/home/oracle/initMASK11G.ora’
LRM-00123: invalid character 128 found in the input file
ORA-01078: failure in processing system parameters