We are running a perl script to upload some data using SQL* Loader. We pipe the data in a http request to SQL*Loader which loads the data to the database. We encounter the error "Inappropirate ioctl for device" when we try to upload huge data. Any solution would be greatly appreciated.
Could you be more specific? It seems as though you are trying to invoke sqlldr interactively. This error can happen when you try to invoke an interactive utility like sqlldr in a scripted fashion.
You can use a here document to invoke sqlldr with the interactive prompts:
sqlldr doesn't require interaction though so you can provide all the necessary information on the command line.
When I try to format a slice in Solaris 10 I get the follow error :confused: :
-bash-3.00# mkfs /dev/dsk/c1d0s5 18877824
Can not determine partition size: Inappropriate ioctl for device
Some format command output:....
AVAILABLE DISK SELECTIONS:
0. c1d0 <DEFAULT cyl 38735 alt 2... (0 Replies)
Hello,
I have a cron entry:
59 23 * * * . $HOME/.profile;mydate=`date '+%Y%m%d'`;mv filename filename_$mydate
Which works fine interactively, but gives me the following error when it runs in cron:
Your "cron" job on servername
. $HOME/.profile;mydate=`date '+
produced the... (4 Replies)
When I try to format a slice in Solaris 10 I get the follow error :
-bash-3.00# mkfs /dev/dsk/c1d0s5 18877824
Can not determine partition size: Inappropriate ioctl for device
Some format command output:....
AVAILABLE DISK SELECTIONS:
0. c1d0 <DEFAULT cyl 38735 alt 2 hd 64 sec 63>... (2 Replies)
Dear all,
Problem goes like this:
I have a shell script which when run manually runs perfectly.
When same script is executed through a job schdeduler I get an error as Inappropriate ioctl for device and the script fails.
This problems seems quite guiling to me.
Any clues are heartly... (11 Replies)
Hello guys,
on my Red Hat machine the /bin/mt status command gives the output dev/tape: inappropriate ioctl for device. This messages comes up after the Server has been rebooted.
Anybody an idea?
Thx
masterofdesaster (8 Replies)
Hi All,
Am finding performance of my SD card using hdparm.
Code:
hdparm -tT /dev/BlockDev0
/dev/BlockDev0:
Timing cached reads: 1118 MB in 2.00 seconds = 558.61 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate
ioctl for device
Timing buffered disk... (1 Reply)
Hello everyone
I am finishing a script allowing me to purge logs on multiple servers, i have one last pb with the ssh command.........it is throwing me the following error :
tcgetattr: Inappropriate ioctl for device (full screen in attached file 1, full script in attached file 2)
It... (15 Replies)
Hi!
I am getting a nohup issue on mac osx while trying to start a process through nohup in the startup script.
nohup: can't detach from console: Inappropriate ioctl for device
Please help!
Thanks,
Allan. (0 Replies)
Hi,
ssh -q -t -l $usr $host bin/test.sh
I am using above command to run script remotely. script is working without any issues. but I am getting "tcgetattr: Inappropriate ioctl for device" message on console.
plz help how can I avoid this message.
Thanks
Moved thread from Emergency... (1 Reply)
Sample program tty, this will be get called from my script test_script.
#include <stdio.h>
#include <unistd.h>
#define TTY_NAME_MAX 32
#define STDIN_FILENO 0 /* Standard input. */
int main(void) {
int ret = 0;
char local_device_file;
printf("\npid =... (7 Replies)
Discussion started by: Gajendra_PH
7 Replies
LEARN ABOUT DEBIAN
bsqldb
bsqldb(1) FreeTDS Utilities bsqldb(1)NAME
bsqldb - batch SQL script processor using DB-Library
SYNOPSIS
bsqldb [-U username] [-P password] [-S servername] [-D database]
[-i input_file] [-o output_file] [-e error_file] [-H hostname]
[-t field_term] [-hqv]
DESCRIPTION
bsqldb is a utility program distributed with FreeTDS.
bsqldb is a non-interactive equivalent of the "isql" utility programs distributed by Sybase and Microsoft. Like them, bsqldb uses the com-
mand "go" on a line by itself as a separator between batches. The last batch need not be followed by "go".
bsqldb makes use of the DB-Library API provided by FreeTDS. This API is of course also available to application developers.
OPTIONS -U username
Database server login name. If username is not provided, a domain login is attempted for TDS 7+ connections.
-P password
Database server password.
-S servername Database server to which to connect.
-D database
Database to use.
-i input_file
Name of script file, containing SQL.
-o output_file
Name of output file, holding result data.
-e error_file
Name of file for errors.
-t field_term
Specifies the field terminator. Default is two spaces (' '). Recognized escape sequences are tab (' '), carriage return ('
'),
newline ('
'), and backslash ('\').
-h Print column headers with the data to the same file.
-H hostname Override name of client sent to server.
-q Do not print column metadata, return status, or rowcount. Overrides -h.
-v Verbose mode, for more information about the DB-Libraryrary interaction. This also reports the result set metadata, including and
return code. All verbose data are written to standard error (or -e), so as not to interfere with the data stream.
ENVIRONMENT
DSQUERY
default servername
NOTES
bsqldb is a filter; it reads from standard input, writes to standard output, and writes errors to standard error. The -i, -o, and -e
options override these, of course.
The source code for bsqldb is intended as a model for DB-Library users. DB-Library has a rich set of functions, and it can be hard some-
times to understand how to use them, particularly the first time. If you are using it in this way and find something unclear, you are
encouraged to email the author your comments.
EXIT STATUS
bsqldb exits 0 on success, and >0 if the server cannot process the query.
bsqldb will report any errors returned by the server, but will continue processing. In a production environment, this behavior may be
insufficiently stringent. To make it extremely intolerant of errors, change the message and error handlers to call exit(3).
HISTORY
bsqldb first appeared in FreeTDS 0.63.
AUTHORS
The bsqldb utility was written by James K. Lowden <jklowden@schemamania.org>
BUGS
Microsoft servers as of SQL Server 7.0 SP 3 do not return output parameters unless the RPC functions are used. This means bsqldb cannot
return output parameters for stored procedures with these servers.
doc 13 November 2011 bsqldb(1)