Export Dump file Size
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 10 of 10

Thread: Export Dump file Size

  1. #1
    Join Date
    Mar 2001
    Posts
    36
    Hi,

    I am not able to create export dump file more than 2GB. I Have one table XXX (size 20 GB). for reorg. I tried to export the table but when it reach at 2GB file size export was terminated.

    I checked on OS (AIX 5) level.

    ulimit -a

    time(seconds) unlimited
    file(blocks) unlimited
    data(kbytes) 262144
    stack(kbytes) 32768
    memory(kbytes) 32768
    coredump(blocks) 2097151
    nofiles(descriptors) 2000

    Is their any parameter or env. variable I need to set ..?

    Help me..!!!!

  2. #2
    Join Date
    Dec 2001
    Location
    SAN FRANCISCO, CA
    Posts
    306
    boss u have to give the parameter FILE as file=file1.dmp,file2.dmp,file3.dmp and so on..
    Eat , Drink & Enjoy life -

    pravin_kini@hotmail.com

  3. #3
    Join Date
    Oct 2000
    Location
    Charlotte, USA
    Posts
    330
    Hi,
    create a pipe and compress the dump file.
    You will be all right.
    Thanks.
    Thanigaivasan.

  4. #4
    Join Date
    Nov 1999
    Posts
    226

    can you give the syntax for the pipe

    can you give the syntax for the pipe

  5. #5
    Join Date
    Nov 2000
    Posts
    101
    Hi,

    What is your Oracle Version. If it is 8 then the dump file size is 2 GB maximum.

    Go for file=a.dmp,b.dmp,c.dmp etc...


    Cheers
    gandhi
    OCP8-DBA.


  6. #6
    Join Date
    Feb 2000
    Location
    Singapore
    Posts
    1,758
    Originally Posted by: gandhi
    What is your Oracle Version. If it is 8 then the dump file size is 2 GB maximum.

    Go for file=a.dmp,b.dmp,c.dmp etc...
    Oracle doesn't have the limit of 2GB file size some of the unix OS are having a limit of 2GB.
    I did export/import over 2GB on Oracle7 also, that was on Compaq Tru64

    Sanjay

  7. #7
    Join Date
    Jan 2002
    Location
    Up s**t creek
    Posts
    1,525
    He's an example of exporting to a pipe (it's a Solaris script but you should be able to modify it for your own env.)

    # set -x
    #
    # Check syntax of command.
    #
    if [ $# -eq 0 ] ; then
    echo "[ExpPipe] Usage :ExpPipe ORACLE_SID EXPORT_DIRECTORY"
    exit 2
    fi

    #
    # Define funtions
    #
    check_logfile ( )
    {
    grep "Export terminated unsuccessfully" $1
    return $?
    }

    #
    # Define variables
    #
    NOW=`date "+%y%m%d.%H:%M:%S"`
    CURRENTDIR=`dirname $0`
    if [ ${CURRENTDIR} = "." ] ; then
    CURRENTDIR=`pwd`
    fi
    EXPORT_DIR=$2
    if [ $2 -eq 0 ] ; then
    EXPORT_DIR=`pwd`
    fi
    ORG_ORACLE_SID=$ORACLE_SID
    OPTIONS1="consistent=yes buffer=1000000 statistics=NONE full=yes"
    OPTIONS2="buffer=1000000 statistics=NONE full=yes"
    PIPENAME=/tmp/ExpPipe.${ORACLE_SID}.$$
    LOGFILE=./ExpPipe_log.${ORACLE_SID}.${NOW}
    EXPORTFILE=${EXPORT_DIR}/exp.${ORACLE_SID}.${NOW}

    #
    # Set up oracle environment
    #
    export ORACLE_SID=$1
    ORAENV_ASK=NO
    . oraenv

    #
    # Perform export
    #
    /usr/sbin/mknod $PIPENAME p
    exp userid=/ file=${PIPENAME} ${OPTIONS1} log=$LOGFILE.1 1>>/dev/null 2>&1 &
    dd if=${PIPENAME} 2>>/dev/null | compress -c > ${EXPORTFILE}.consistent.Z

    check_logfile ${LOGFILE}.1

    if [ $? -eq 0 ]
    then
    rm ${EXPORTFILE}.consistent
    else
    rm ${PIPENAME}
    exit 0
    fi

    exp userid=/ file=${PIPENAME} ${OPTIONS2} log=$LOGFILE.2 1>>/dev/null 2>&1 &
    dd if=${PIPENAME} 2>>/dev/null | compress -c > ${EXPORTFILE}.Z

    rm ${PIPENAME}

    #
    # Reset environment
    #
    export ORACLE_SID=$ORG_ORACLE_SID
    ORAENV_ASK=NO
    . oraenv


    Regards
    Jim
    Oracle Certified Professional
    "Build your reputation by helping other people build theirs."

    "Sarcasm may be the lowest form of wit but its still funny"

    Click HERE to vist my website!

  8. #8
    Join Date
    Jan 2001
    Posts
    3,131
    I think the 2 gig file limit is more a product of the OS, Unix can have this limitation unless you have large files enabled. This is how it works in my shop with HP/UX.

    The only heads up I want to throw out there is that if you do choose to compress the .DMP file during export, you will need to know how to uncompress it during an import. If the uncompressed .DMP file is larger that 2 gigs uncompressed, you will not be able to open it via uncompress since your mount point will puke on you.

    There is a way to read and use the compressed .DMP file without opening it but I am not sure how this works.
    Anyone?
    Do you just reverse the pipe?

    MH
    I remember when this place was cool.

  9. #9
    Join Date
    Mar 2001
    Posts
    36
    I'm doing reorg. using SAP's SAPDBA tool, Oracle Ver. is 7.3
    And during export of table it will not allow for file size more than 2GB.


    ?????

  10. #10
    Join Date
    Nov 2000
    Posts
    101
    Hi Patel,

    Could tell us the O/S you are using with Version.



    bye
    gandhi
    OCP8-DBA

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width