Syntax Error near Database name

Hi,
When i tried to take export from automated process (Not Manually) from a application its giving error like :
ERROR - 1242021 - (1) Syntax error near ['Currency'].
The type of database is Currency.
But if i take the export Manually form Essbase application Manager, i can sucessfully perform the activity.
Now ......
1.Type of database and Name (Currency) Can be Equal ??????
2.The Automated Process can't be wrong because export of different DB is sucessful with this Automated Process.
Please suggest.
Thanks,
Kaash

Hi Kaash
I had a similar issue in when I used a db name of 'Volume', I also wonder whether there are certain restricted words that you shouldn't use due to conflicts with MaxL / Esscmd?
I overcame it by re-naming to 'Volumes'.
Hope this helps, or at least reassures you that you're not going mad!
Stuart

Similar Messages

Reverse error when database name includes just numbers

I have a sql server 2000 source and one of its database named 10053. When I created physical architecture and logical architecture, ODI all returned ok. But when I did reversing, ODI returned this error: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer] first line: there is a syntax error near '10053'. I did a experiment to use another sqlserver source named 'aaa', the error dispeared. So I think that ODI does not support digital sqlserver database name. Is it true? To finish this interface, what can I do except for changing the db name?
Thanks!

You may also search for Access help at http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US

Forms 10g compile : syntax error near unexpected token `in

Hi,
I am writing a code to compile FORMS 10g(10.1.2.0.2) in HP_UX one by one.
this is the code---frm10g.sh
*#!/bin/ksh*
*# . ~oracle/forms/server/default.env*
*# . sid icache*
TERM=vt220
*if [ $# != 2 ]*
then
echo Usage : $0 module_name module_type
exit 1
fi
case $2 in
FORM|form|F|f) ext1='fmb' ;ext='fmx' ; modtyp='FORM' ;;
PLL|pll|p|lib|LIB) ext1='pll' ;ext='plx' ; modtyp='LIBRARY' ;;
MENU|menu|M|m) ext1='mmb' ;ext='mmx' ; modtyp='MENU' ;;
**) echo invalid parameter ; exit 1 ;*
esac
echo Generating $1.$ext
frmcmp module=$1.$ext1 userid=abc/abc@abc output_file=../$1.$ext module_type=$modtyp batch=NO compile_all=special > ./log/$1.log
when I try to excute above file frm10g.sh in command line i get following error. Please let me know how to fix it.
[abc]u01/app/oracle/product/10.1.2/forms/forms/Forms10g:. frm10g.sh INV FORM
: command not found
: command not found
'bash: ./frm10g.sh: line 13: syntax error near unexpected token `in
'bash: ./frm10g.sh: line 13: `case $2 in
I really aapreciate your help.
Thanks
Sandy

Sandy,
I must apologize. The Compile.sh does not come with the Oracle Dev Suite installation. However, the following is the contents of the compile.sh script we use. This script compiles a single form.
#!/usr/bin/ksh
ORACLE_HOME=/d01/oracle/ias1012;export ORACLE_HOME
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32:$ORACLE_HOME/ctx/lib:/usr/java1.2/jre/lib/sparc:$ORACLE_HOME/jdk/jre/lib/sparc:/usr/lib:/usr/dt/lib:/usr/openwin/lib:/usr/ucblib:usr/ccs/lib; export LD_LIBRARY_PATH
MODULE_NAME=`echo $1|cut -d. -f1`
MODULE_SUFFIX=`echo $1|cut -d. -f2`
MODULE_MESG=${2:-"Compiling $1"}
OK_MESG=${3:-" Compiled sucessfully"}
. .setpass_cir
APP_PW='cir/'`eimauth -g cir`'@database'
echo "************************************************************************* "
echo ${MODULE_MESG}
frmcmp.sh module=/d01/oracle/forms/${MODULE_NAME}.fmb userid=${APP_PW} compile_all=yes batch=yes
RC=$?
case "$RC" in
0)
    echo ${OK_MESG}
    echo "Compile errors, return code: $RC "
    cat ${MODULE_NAME}.err
    echo "Compile errors in $1, press [enter] to continue.\c"
    read x
esac
eval exit $RCYou should be able to modify this to suit your needs.
Craig...

ERROR - 1242021 - (1) Syntax error near ['security_file']

When invoking the command "export security_file to data_file essbase_security_file.txt;" I get the error message "ERROR - 1242021 - (1) Syntax error near \['security_file'\]". I get the same message from EAS when right clicking and exporting from the console. The end game here is that I want to dump the Essbase.sec file into a readable format.
Any help appreciated.
Thanks
-Kevin
Edited by: user5439694 on Dec 31, 2009 11:58 AM
Edited by: user5439694 on Dec 31, 2009 11:59 AM

IT is easier to just go into EAS and select the Essbase server, then right click on Security and select export security file. Enter the file name you want it to go to. In Version 11 it puts the file in Arborpath\Products\Essbase\EssbaseServer\Bin
I also ran the following MaxL export security_file to data_file 'e:\datafiles\security_test.txt';
and it ran fine (It put the file onto the Essbase server in the specified directory)

Syntax error near unexpected token `)'

I get that error sometimes when i try to complile. I was trying to use my Banshee1.5.1 PKGBUILD on my desktop (it works on my laptop) and i got that error again. But i don't think it's banshee cause i remember getting that same error when i wanted to complile Gnote.
Banshee
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
./configure: eval: line 2650: unexpected EOF while looking for matching `''
./configure: eval: line 2651: syntax error: unexpected end of file
configure: WARNING: `missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether NLS is requested... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for intltool >= 0.35.0... 0.41.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for a BSD-compatible install... /bin/install -c
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ANSI C header files... (cached) yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.0.0... yes (version 2.22.2)
checking for GDK_X11... yes
checking for CLUTTER... yes
checking for GST... yes
checking for GST_PBUTILS... yes
checking for BNPX_GTK... yes
checking for X... libraries , headers
checking for XVIDMODE... yes
checking for MONO_MODULE... yes
checking for gmcs... /usr/bin/gmcs
checking for mono... /usr/bin/mono
checking for Mono 2.0 GAC for System.Data.dll... found
checking for Mono 2.0 GAC for System.Web.dll... found
checking for Mono 2.0 GAC for System.Web.Services.dll... found
checking for Mono 2.0 GAC for Mono.Cairo.dll... found
checking for Mono 2.0 GAC for Mono.Posix.dll... found
checking for Mono 2.0 GAC for ICSharpCode.SharpZipLib.dll... found
checking for NDESK_DBUS_GLIB... yes
checking for NDESK_DBUS... yes
checking for MONO_ADDINS... yes
checking for MONO_ADDINS_SETUP... yes
checking for MONO_ADDINS_GUI... yes
checking for NOTIFY_SHARP... yes
checking for BOO... yes
checking for monodocer... /usr/bin/monodocer
checking for mdassembler... /usr/bin/mdassembler
checking for NUNIT... no
checking for NUNIT... yes
checking for TAGLIB_SHARP... yes
checking for GTKSHARP... yes
checking for GLIBSHARP... yes
checking for SQLITE... yes
checking for GCONFSHARP... yes
checking for GNOMESHARP... yes
checking for gconftool-2... /usr/bin/gconftool-2
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for LIBMTP... yes
checking for struct LIBMTP_track_struct.modificationdate... no
checking for IPODSHARP... yes
checking for KARMASHARP... no
checking for MONO_ZEROCONF... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for catalogs to be installed... ar be@latin bg br ca cs da de dz en_CA en_GB es eu fi fr gl gu he hu it ja ko ky lt lv mk nb nl oc pa pl pt pt_BR ru sl sr sr@latin sv th uk vi zh_CN zh_HK zh_TW
checking for sed... /bin/sed
configure: creating ./config.status
./config.status: line 400: syntax error near unexpected token `)'
./config.status: line 400: ` *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;'
Gnote
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
./configure: eval: line 2411: unexpected EOF while looking for matching `''
./configure: eval: line 2412: syntax error: unexpected end of file
configure: WARNING: `missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for LIBGLIBMM... yes
checking for GTK... yes
checking for LIBGTKMM... yes
checking for LIBXML... yes
checking for LIBXSLT... yes
checking for GCONF... yes
checking for PCRE... yes
checking uuid/uuid.h usability... yes
checking uuid/uuid.h presence... yes
checking for uuid/uuid.h... yes
checking for uuid_unparse_lower in -luuid... yes
checking for LIBPANELAPPLETMM... yes
checking for GTKSPELL... yes
checking for Boost headers version >= 103400... yes
checking for Boost's header version... 1_39
checking boost/bind.hpp usability... yes
checking boost/bind.hpp presence... yes
checking for boost/bind.hpp... yes
checking boost/cast.hpp usability... yes
checking boost/cast.hpp presence... yes
checking for boost/cast.hpp... yes
checking boost/lexical_cast.hpp usability... yes
checking boost/lexical_cast.hpp presence... yes
checking for boost/lexical_cast.hpp... yes
checking for the toolset name used by Boost for g++... gcc44 -gcc
checking boost/system/error_code.hpp usability... yes
checking boost/system/error_code.hpp presence... yes
checking for boost/system/error_code.hpp... yes
checking for the Boost system library... yes
checking boost/filesystem/path.hpp usability... yes
checking boost/filesystem/path.hpp presence... yes
checking for boost/filesystem/path.hpp... yes
checking for the Boost filesystem library... yes
checking boost/format.hpp usability... yes
checking boost/format.hpp presence... yes
checking for boost/format.hpp... yes
checking boost/test/unit_test.hpp usability... yes
checking boost/test/unit_test.hpp presence... yes
checking for boost/test/unit_test.hpp... yes
checking for the Boost unit_test_framework library... yes
checking tr1/memory usability... yes
checking tr1/memory presence... yes
checking for tr1/memory... yes
checking whether gcc understands -Wall... yes
checking whether gcc understands -Wextra... yes
checking whether gcc understands -Wsign-compare... yes
checking whether gcc understands -Wpointer-arith... yes
checking whether gcc understands -Wchar-subscripts... yes
checking whether gcc understands -Wwrite-strings... yes
checking whether gcc understands -Wunused... yes
checking whether gcc understands -Wpointer-arith... yes
checking whether gcc understands -Wshadow... yes
checking whether gcc understands -fshow-column... yes
checking whether NLS is requested... yes
checking for intltool >= 0.35.0... 0.41.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.10.1
checking for XML::Parser... ok
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for gconftool-2... /usr/bin/gconftool-2
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for sed... /bin/sed
configure: creating ./config.status
./config.status: line 400: syntax error near unexpected token `)'
./config.status: line 400: ` *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;'
Both get exactly the same error.

I have tried downgrading bash and gcc, but no luck. I have also looked into some config files and stuff but i can't find anything. Maybe it's time for a reinstall.

Syntax error near the ['on']

Can anyone please advise on how to resolve this issue, I created Dim load file but whenever I try loading the Dim it returns - syntax error near the ['on']
thanks

I don't see the issue
Delimiter was set as comma, first line was ignored and it all loaded fine.
Cheers
John

/etc/init.d/nodemgr: line 96: syntax error near unexpected token `is'

I am trying to modify the unix script to auto start nodemanager on Oracle Linux server,however i am getting below error when ever i tried to start service nodemgr restart
here is script:
============
#!/bin/sh
# nodemgr Oracle Weblogic NodeManager service
# chkconfig: 345 85 15
# description: Oracle Weblogic NodeManager service
# The script needs to be saved as /etc/init.d/nodemgr and then issue chkconfig .add nodemgr as root
### BEGIN INIT INFO
# Provides: nodemgr
# Required-Start: $network $local_fs
# Required-Stop:
# Should-Start:
# Should-Stop:
# Default-Start: 3 4 5
# Default-Stop: 0 1 2 6
# Short-Description: Oracle Weblogic NodeManager service.
# Description: Starts and stops Oracle Weblogic NodeManager.
### END INIT INFO
. /etc/rc.d/init.d/functions
export WLS_HOME=/u01/Oracle/Middleware/wlserver_10.3
export MW_HOME=/u01/Oracle/Middleware
export JAVA_HOME=/u01/Oracle/Middleware/jdk160_24
export IDM_HOME=/u01/Oracle/Middleware/Oracle_IDM1
export OAM_HOME=/u01/Oracle/Middleware/Oracle_IDM2
export ORACLE_INSTANCE=/u01/Oracle/Middleware/Oracle_IDM1
export IAM_HOME=/u01/Oracle/Middleware/Oracle_IDM2
export DOMAIN_HOME=/u01/Oracle/Middleware/user_projects/domains
DAEMON_USER="oracle"
PROCESS_STRING="^.*/u01/Oracle/Middleware/.*weblogic.NodeManager.*"
source $MW_HOME/wlserver_10.3/server/bin/setWLSEnv.sh > /dev/null
export NodeManagerHome="$WLS_HOME/common/nodemanager"
NodeManagerLockFile="$NodeManagerHome/nodemanager.log.lck"
PROGRAM="$MW_HOME/wlserver_10.3/server/bin/startNodeManager.sh"
SERVICE_NAME=`/bin/basename $0`
LOCKFILE="/var/lock/subsys/$SERVICE_NAME"
RETVAL=0
start() {
OLDPID=`/usr/bin/pgrep -f $PROCESS_STRING`
if [ ! -z "$OLDPID" ]; then
echo "$SERVICE_NAME is already running (pid $OLDPID) !"
exit
fi
echo -n $"Starting $SERVICE_NAME: "
/bin/su $DAEMON_USER -c "$PROGRAM &"
RETVAL=$?
echo
[ $RETVAL -eq 0 ] && touch $LOCKFILE
stop() {
echo -n $"Stopping $SERVICE_NAME: "
OLDPID=`/usr/bin/pgrep -f $PROCESS_STRING`
if [ "$OLDPID" != "" ]; then
/bin/kill -TERM $OLDPID
else
/bin/echo "$SERVICE_NAME is stopped"
fi
echo
/bin/rm -f $NodeManagerLockFile
[ $RETVAL -eq 0 ] && rm -f $LOCKFILE
restart() {
stop
sleep 10
start
case "$1. in
start)
start
stop)
stop
restart|force-reload|reload)
restart
condrestart|try-restart)
[ -f $LOCKFILE ] && restart
status)
OLDPID=`/usr/bin/pgrep -f $PROCESS_STRING`
if [ "$OLDPID" != "" ]; then
/bin/echo "$SERVICE_NAME is running (pid: $OLDPID)!"
else
/bin/echo "$SERVICE_NAME is stopped"
fi
RETVAL=$?
echo $"Usage: $0 start"
exit 1
esac
exit $RETVAL
=================
here is error message
[root@oam init.d]# service nodemgr restart
/etc/init.d/nodemgr: line 96: syntax error near unexpected token `is'
/etc/init.d/nodemgr: line 96: `/bin/echo "$SERVICE_NAME is running ("pid: $OLDPID")"'

It is necessary to post code between code tags, otherwise it screws up. See the FAQ.
What sticks out right away is your wrong case statement case *"$1.* which should read *case "$1"*. You are also missing ;; to terminate your default case statement. You should also put $RETVAL between quotes and remove the /bin paths.

MySQl syntax error near " at line 1 and Unknown column. Please help

Hello again,
I have another question. Just to refresh I am using DWCS3 with MAMP on my MBP Leopard 10.5.6.
I have created a form with the form wizard and a Transitional <!DOCTYPE>
I have added the php validation code pages 481 to 485 The Essential Guide to Dreamweaver.
I saved it and uploaded it to the testing server clicked the "insert form" button,and I got;
You have an error in your SQL syntax; Check the manual that corresponds to your MySQL server version for the right syntax to use near " at line 1
The MySQL version I am using is 5.0.37. I have gone over and over the code and I can't find what is wrong with it.
Also for the username column, I am now getting a message;
'Unknown column' 'ella1' in 'where clause'
I have researched it on the web and possible answers are that my columns are misspelled, the column doesn't exist or username is not in the query.
I have checked all of these and I really can't see the problem, but there obviously is one.
Please can someone help.
Thanks again.
P.S. I have attached the page in a .zip file if anyone wouldn't mind having a look.

No, I'm talking about the dot before.
Change this
.$row_detailsRS[$details_prodID] . "";
to this
. $row_detailsRS[$details_prodID] . "";
in both places.

Predictive Analysis error message "[Sybase][ODBC Drivers][Sybase IQ]Syntax error near ',' on line 1

Hello,
I have a custom R component with a function that reads data from a hard configured file.
No database operations but I get this ODBC error that, I suppose, originates from PA talking to the IQ server it runs.
How can I find more about what PA tries to do, especially can I get a trace of the SQL it tries to execute?
Best regards,
Andreas

Hi Andreas,
You could start by looking at the logfiles that SAP PA produces.
From your Windows Explorer go to the directory: %temp%\sapvi\logs
Here you will find the logfiles that PA creates - as an example:
If this information is not covering your requirements turn to the SAP PA manuel on page 11, section 5.4 configuring logs where it is described how to do a custom tracing.
Good luck.
Best regards,
Kurt Holst

Syntax error when creating database

Not sure if this is the correct forum, but here goes..
Using a sample at:
Technet Link
I get a "Syntax error near GO" when I try to execute the following SQL Command.
USE master
GO
CREATE DATABASE testdb
ON
( NAME = testdb,
FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\testdb.mdf' )
GO
I am using a function to create this database. It is a temporary database that gets recreated or altered frequently.
The code checks for SQL Server, gets it's version number in order to use the default SQL Server path. If SQL Server isn't available, ACE / OLEDB is used to create and manage the database (this part works fine).
The code used to check for and create the database follows.
private Boolean CheckForSQLServer()
SqlConnection cnx = null;
Int32 dbExists = 1;
SqlCommand sql;
String SSData = String.Empty;
// Check for SQL Server. If it exists, use it.
String login = UserPrincipal.Current.UserPrincipalName;
login = login.Substring(0, login.IndexOf("@"));
try {
cnx = new SqlConnection(
String.Format("server={0};user={1};Trusted_Connection=Yes;", Prop.SQLConnection, login));
cnx.Open();
hasSQLServer = true;
} catch (Exception) {
hasSQLServer = false;
return true;
if (hasSQLServer) {
try {
String ServerVersion = cnx.ServerVersion;
String SSPath = String.Format(@"C:\Program Files\Microsoft SQL Server\MSSQL{0}.MSSQLSERVER\MSSQL\DATA\",
ServerVersion.Substring(0, ServerVersion.IndexOf('.')));
SSData = String.Format(
"USE master\nGO\nCREATE DATABASE {0}\nON\n( NAME = '{1}',\nFILENAME = '{2}{1}.mdf' )\nGO",
Prop.SQLDBName, Prop.SQLDBName, SSPath);
String s = String.Format(
"SELECT COUNT(*) FROM (SELECT DB_ID('{0}') AS DbID) t WHERE DbID IS NOT NULL", Prop.SQLDBName);
sql = new SqlCommand(s, cnx);
SqlDataReader sr = sql.ExecuteReader();
if (sr.Read())
dbExists = (Int32)sr[0];
sr.Close();
} catch (Exception) { }
if (dbExists == 0) {
try {
sql = new SqlCommand(SSData, cnx);
sql.ExecuteNonQuery();
} catch (Exception) { }
} else {
try {
sql = new SqlCommand(String.Format("drop database {0};", Prop.SQLDBName), cnx);
sql.ExecuteNonQuery();
sql = new SqlCommand(SSData, cnx);
sql.ExecuteNonQuery();
} catch (Exception) { }
cnx.Close();
return false;
Comparing the generated SQL string to sample E at the link above shows them to be identical except for the database name and file pathname, but the paths do exist although the files do not.
The SQL Exception occurs at the first
sql = new SqlCommand(SSData, cnx);
statement in the code. I would think this can be done as a single string even though a .sql file is referenced in the article.
Andy

Works correctly in SQL Server 2014 Management Studio:
USE master
GO
CREATE DATABASE testdb
ON
( NAME = testdb,
FILENAME = 'F:\temp\testdb.mdf' )
GO
DROP DATABASE testdb
GO
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Syntax error Creating Transparent Partition in MaxL

Hello,
I'm trying to create a simple transparent partition (no mapping needed, just using all the 3 dimensions and descendants in the source database to the target database. I'm getting a syntax error, I went through the MaxL naming conventions and also tried a couple of diffferent things but to no avail. Please help as to what the error might be:
My code is as below. The error I get is: Getting a syntax error near '@IDESCENDANTS("Accounts"), @IDESCENDANTS("Products"),@IDESCENDANTS("Market)
Code:
create transparent partition student8.coke area '@IDESCENDANTS("Accounts"), @IDESCENDANTS("Products"),@IDESCENDANTS("Market")' sourceArea to student8.cokepart at lab01 as essadmin identified by 'password' area '@IDESCENDANTS("Accounts"), @IDESCENDANTS(Products), @IDESCENDANTS("Market")' targetArea;

Nobody replied to this, but actually the error was the double quotes on Accounts, Products and Market.

Error - 1242021 Syntax error

So I am attempting to grant access for JExport. Please help.
MAXL> grant codeBase "file:\\Hyperion\AnalyticServices\java\udf\ExportCDF.jar" {
permission java.security.AllPermission};
I am receiving this message:
ERROR - 1242021 - (1) Syntax error near ['codeBase'].
I have no idea if this is where I am suppose to enter this in or what.
PLEASE HELP!

This should be a value you add to the udf.policy file on the server. It is not something MaxL can do for you. If on Window, notpad will work fine, if on UNIX VI

Makepkg syntax error - caused by POSIXLY_CORRECT

I'm new to arch linux and after installation of arch and the first steps with
makepkg I was confronted with following script error:
/usr/bin/makepkg: line 1545: syntax error near unexpected token `<'
/usr/bin/makepkg: line 1545: ` done < <(find . -type f -perm -u+w
-print0 2>/dev/null)'
After a long time checking the script I found the problem in my .zshenv where
the environment variable POSIXLY_CORRECT=1 was exported. After unsetting this,
makepkg worked well.
I've used this to force myself to write scripts that are portable between
different systems, and I'd like to keep this variable set also on my new arch
system. Wouldn't it be a good decision to change the makepkg script to also
work if POSIXLY_CORRECT is set? If the issue is known and POSIX does not
belong to the Arch Way, I'll accept that and will unset POSIXLY_CORRECT before
building a package.

I think you should ask this on the ML or open a feture request on the bugtracker.

CR2011 - SQL Syntax Error

After updating our ODBC driver to match our current Unidata database version (7.1), we now get the following message from Crystal Reports 2011 on many of our existing reports:
"Failed to retrieve data from the database. Details: 37000:[Rocket U2][U2ODBC][1401249]Error ID: 21 Severity: ERROR Facility: DBCAPERR - SQL Syntax error. [Database Vendor Code: 5365440]
The generated SQL statement follows:
SELECT "INVCDETH_NF"."ITEM_NBR", "ITEMMAST_NF"."ITEM_DESC", "INVCDETH_NF"."SHIPPED_QUANTITY", "INVCDETH_NF"."Z_INV_DATE", "INVCDETH_NF"."Z_COMPANY", "INVCHDRH_NF"."INVOICE_TYPE", "INVCDETH_NF"."EXTENDED_PRICE", "INVCDETH_NF"."COST_OF_SALES", "INVCDETH_NF"."Z_PCC_CODE", "INVCDETH_NF"."DISCOUNT_AMOUNT", "INVCDETH_NF"."WAREHOUSE", "ITEMMAST_NF"."PRICE_CODE", "INVCHDRH_NF"."INVOICE_NBR", "INVCHDRH_NF"."REFERENCE_NBR"
FROM ("Administrators"."ITEMMAST_NF" "ITEMMAST_NF" INNER JOIN "Administrators"."INVCDETH_NF" "INVCDETH_NF" ON "ITEMMAST_NF"."ITEM_NBR"="INVCDETH_NF"."ITEM_NBR") INNER JOIN "Administrators"."INVCHDRH_NF" "INVCHDRH_NF" ON ((("INVCDETH_NF"."INVOICE_NBR"="INVCHDRH_NF"."INVOICE_NBR") AND ("INVCDETH_NF"."INV_HEADER_ID"="INVCHDRH_NF"."INV_HEADER_ID")) AND ("INVCDETH_NF"."REFERENCE_NBR"="INVCHDRH_NF"."REFERENCE_NBR")) AND ("INVCDETH_NF"."RELEASE_NBR"="INVCHDRH_NF"."RELEASE_NBR")
WHERE "INVCDETH_NF"."Z_COMPANY"='01' AND "INVCDETH_NF"."WAREHOUSE"='086' AND ("INVCDETH_NF"."Z_INV_DATE">={d '2013-12-08'} AND "INVCDETH_NF"."Z_INV_DATE"<={d '2013-12-26'})
ORDER BY "INVCDETH_NF"."WAREHOUSE"
I downloaded the trial version of CR2013 and get the same result. Can anyone shed any light? Thanks!

Yes, in that the query is what Crystal generated from the report being built in the designer. I simply copied it from the Database > Show SQL Query screen. Since the error I'm receiving is a SQL Syntax Error, I thought it would be appropriate to show it.
The bottom line is that because I am not very knowledgeable in SQL, I can't look at the query and identify the error. However, I am responsible for supporting CR in-house. Naturally, I have reported this to Rocket (the makers of the ODBC driver) but haven't received their reply yet.

Syntax Error in XL Report

Dear All,
When i am generating the XL Report it's give me the like
An error while executing report!
Description: Definition Parsing Failed.
Details:
Syntax Error Near : ItemType_0 at row $11:$16
Syntax Error Near : TotForwarding_0 at row $14:$14
Please suggest on this issue.
Thanks & Regards,
Tushar Nathwani

There are several notes on this issue. After an upgrade these UDF fields can be reset to a diffient value.
In the XL Reporter menu, turn your UDF's off, then on again to reset them.
If they are in your report as _0 values, you may need to delete & re-add them in your definition to pick up the new value.

Syntax Error near Database name

Similar Messages

Maybe you are looking for