Exclude parameter limitations

Hi
is there any limitations for excluding no of objects while doing expdp
when i m excluding 2 table is running
expdp system/**** parfile=q.par
________________________________ q.par__________________________________________________________________________
DIRECTORY=TEST_DIR DUMPFILE=filename.dmp LOGFILE=filename.log SCHEMAS=xyz exclude=TABLE:"IN ('tab1', 'tab2')"
when i m excluding 2000 tables expdp is showing below error
Export: Release 11.1.0.6.0 - 64bit Production on Tuesday, 28 September, 2010 17:08:44
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
UDE-00014: invalid value for parameter, 'exclude'.
plz suggest.

Use a parfile, it should work without issue.
# expdp sysadm/*** dumpfile=test.dmp schemas=sysadm exclude=table:"in (select table_name from my_tables_to_exclude)"
Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 29 September, 2010 9:23:07
Copyright (c) 2003, 2007, Oracle.  All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
ORA-39001: invalid argument value
ORA-39071: Value for EXCLUDE is badly formed.
ORA-00936: missing expression
# more param.par
dumpfile=test.dmp
schemas=sysadm
exclude=table:"in (select table_name from my_tables_to_exclude)"
# expdp sysadm/*** parfile=param.par
Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 29 September, 2010 9:23:24
Copyright (c) 2003, 2007, Oracle.  All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
Starting "SYSADM"."SYS_EXPORT_SCHEMA_02":  sysadm/******** parfile=param.par
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
...Nicolas.

Similar Messages

  • RESTFul URI parameter limitations/bugs

    Hi,
    I've run into some limitations (or bugs, don't know which is the most appropriate term at this point) regarding URI template parameters for RESTful Services. Here are a few examples to illustrate:
    First limitation:
    To start with, I define the following Resource Template: *example?p1={p1}&p2={p2}*
    I use the following query as the GET handler: select :p1, :p2 from dual
    This works fine, the URL example?p1=foo&p2=bar gets a json response like this: {":1": "foo",":2": "bar"}
    I then create a second Resource Template with only the first parameter from the previous template: *example?p1={p1}*
    I use the following query as the GET handler: select :p1 from dual
    This works as expected, however now the previous template returns the following: {":1": "foo&p2=bar"}, i.e. the part of the URI string after p1= gets parsed as a single parameter.
    Second limitation:
    I define the following resource template: *example1/{p1}*
    I use the following query as the GET handler: select :p1 from dual
    Works fine.
    I then define the following resource template: *example1/{p1}/example2*
    I use the same query again as the GET handler: select :p1 from dual. This time the whole part of the URI string from {p1} forward gets parsed as the p1 parameter, which means it returns {":1":"foo/example2"} rather than {":1":"foo"}. However, if I remove the example1/{p1} template, the example1/{p1}/example2 works as expected.
    In both cases, it seems like the rules for URI templates are excessively strict regarding URI similarities with other templates. I've been unable to find any reference to this in the documentation, other than a vague reference to a lack of support for "optional parameters".
    Assuming these are known limitations rather than bugs, might they be removed in a future release?
    Versions:
    APEX Listener 2.0.1
    WLS 10.3.6 on Windows 2008 R2 (64-bit)
    Oracle DB 11.2.0.3
    APEX 4.2.1
    Thanks,
    Tobias

    TobiasE wrote:
    Hi,
    I've run into some limitations (or bugs, don't know which is the most appropriate term at this point) regarding URI template parameters for RESTful Services. Here are a few examples to illustrate:
    First limitation:
    To start with, I define the following Resource Template: *example?p1={p1}&p2={p2}*
    I use the following query as the GET handler: select :p1, :p2 from dual
    This works fine, the URI example?p1=foo&p2=bar gets a json response like this: {":1": "foo",":2": "bar"}
    I then create a second Resource Template with only the first parameter from the previous template: *example?p1={p1}*
    I use the following query as the GET handler: select :p1 from dual
    This works as expected, however now the previous template returns the following: {":1": "foo&p2=bar"}, i.e. the part of the URI string after p1= gets parsed as a single parameter.
    This is when you need to use the priority value to help the listener choose the most appropriate URI Template. Hopefully I can explain what is actually happening and make this a bit clearer.
    The important thing to realise is that a URI Template matches any characters, characters which you might assume are significant to the matching algorithm, the characters which act as delimiters in the URI and query string syntax are not treated as delimiters, they have no special significance, *&*,*=*,*/*,*?* are all treated just the same as any other character . If you look at the final URI Template RFC [1] you can get a feel for how involved it gets trying to specify a URI Template syntax that can robustly match against all common URI patterns, and actually describe a syntax that is aware of the significance of these delimiters.
    So it's your second Resource Template that is matching both URIs and the first one is not getting invoked at all.
    *example?p1={p1}&p2={p2}* matches example?p1=foo&p2=bar, i.e. *{p1}* is mapped to foo and *{p2}* is mapped to bar
    *example?p1={p1}* matches both example?p1=foo and example?p1=foo&p2=bar, i.e. in the first case *{p1}* is mapped to foo and in the second case *{p1}* is matched to: foo&p2=bar
    In plain english the second template means ' match *{p1}* against any text occuring after: example?p1= '
    So when faced with trying to find the appropriate resource template for the URI, listener finds two matching resource templates, which one does it choose?
    The answer is it chooses the one with the highest priority, but if they are both the same priority, then (and admittedly this isn't documented anywhere, it may be subject to change in future releases) it chooses the resource template that requires the least number of parameters to achieve a match (this is just a basic heuristic to help make a choice, it's a bit of a coin toss whether it matches what the developer might have intended).
    So the solution is to give the Resource Templates different priorities, it's up to you to figure out the order in which you want listener to match your templates that match a given URI. Give the template you want checked first the highest priority, the template you want checked second a lower priority.
    So to fix this problem give *example?p1={p1}&p2={p2}* priority of 9 (or any value > the default of 0) and that should solve the problem
    Second limitation:
    I define the following resource template: *example1/{p1}*
    I use the following query as the GET handler: select :p1 from dual
    Works fine.
    I then define the following resource template: *example1/{p1}/example2*
    I use the same query again as the GET handler: select :p1 from dual. This time the whole part of the URI string from {p1} forward gets parsed as the p1 parameter, which means it returns {":1":"foo/example2"} rather than {":1":"foo"}. However, if I remove the example1/{p1} template, the example1/{p1}/example2 works as expected.
    This is the same issue again really, change the priority of *example1/{p1}/example2* to be greater than the priority of *example1/{p1}*.
    In both cases, it seems like the rules for URI templates are excessively strict regarding URI similarities with other templates. I've been unable to find any reference to this in the documentation, other than a vague reference to a lack of support for "optional parameters".
    Assuming these are known limitations rather than bugs, might they be removed in a future release?
    So as you can see these are known limitations, rather than bugs.
    Without committing to anything, I would certainly like to support more of the final URI Template RFC, but as you can see if you read it, there is a fair bit of complexity involved in doing so. A large part of the problem is that URI Templates were really envisaged for the inverse of how we use them (and how other server side frameworks like RESTlet and .NET use them). URI Templates as specified are primarily intended to be used on the client side to form request URIs from a URI Template and parameter values. We're using them the other way round, trying to decode request URIs to match against templates and thereby extract parameter values (to pass into our queries).
    For now I'm not in a hurry to add more support, until we see compelling cases where the above prioritization mechanism cannot solve the matching problem, so would be glad to hear back from you if find scenarios that are not supportable at the moment.
    Regards,
    Colm
    [1] http://tools.ietf.org/html/rfc6570

  • Dynamic Page Parameter Limitations

    Parameters (bind variables) do not seem to be equivalent to string literals when passed to other procedures.
    Try this:
    1)create dynamic page
    2)make the contents call a known function [oracle]begin htp.print(portal30.wwsec_api.id('portal30')); end;[oracle]
    3)run successfully
    Now try this:
    1) change the literal 'portal30' to a dynamic param (:usr)
    2) run from the customize link entering portal30 for usr
    3) unsuccessful
    Why isn't the bind variable style parameter equivalent to a string literal when it is forwarded?

    Could someone see if this works for them - it takes just a moment. I'm really perplexed. When I pass the bind variable to dbms output, it looks right.

  • Exclude records in a parameter selection

    Post Author: bilbo
    CA Forum: General
    Hi,
    Is it possible to exclude records from a parameter selection field? Part of my record selection is: "NOT ({TABLE1.FIELD1} IN {?Exclude})" but my Exclude parameter obviously returns every record. Users need this to exclude multiple selections. Can I limit what is returned by adding a WHERE clause like "NOT ({TABLE1.FIELD1} IN {?Exclude}) WHERE {TABLE1.FIELD2} = 'Car parts' Obviously not what I've just put as this don't work!?!
    I don't really want to manually set the default selections as there is a huge number to contend with.
    Any help or pointers greatly appreciated!
    Bill

    Post Author: SKodidine
    CA Forum: General
    Your NOT condition seems to be fine (at least in CR XI).  You said it is 'part' of the select.  Could it be that the rest of the selection criteria be causing issues?  Also, is your parameter set up to accept multiple values?

  • How to do a full export and exclude user specific tables

    Hi all,
    Is it possible to export all objects but one (or more) tables with expdp when doing a full export?
    This is what I've to in mind: (parfile)
    directory=expdp
    dumpfile=full.dmp
    logfile=full.elog
    full=y
    exclude=table:"IN('userA.table_A')"
    This par-file does not encounter any error messages but it doesn't exclude table_A in schema userA either.
    I guess that's because the the term userA is not interpreted as an owner.
    It's not a big deal to filter out a table when doing a schema export.
    I wonder whether it is at all possible do except a table from a full export. If so, I'd value your suggestions.
    Regards,
    Louis

    Louis,
    The exclude parameter in DataPump takes only the object name, not the schema name. So, if you only have one table called 'TableA', then you can just use:
    exclude=table:"IN('table_A')"
    If you have more than one table called 'table_A', then the exclude will exclude all of them. There is no way to specify user_1.table_a with an exclude parameter.
    Dean

  • Exclude in data pump

    Hi all,
    We are using oracle 10g with windows platform. During the export operation,
    we are using the command EXCLUDE=SCHEMA:"='HR'" for excluding the schema HR.
    Can anybody suggest me about the syntex, if need to exclude more than one schemas
    by using the EXCLUDE parameter?

    This is just an expression clause. You used the 'equal' sign. There is no reason you can't use the 'IN' clause.
    You used:
    EXCLUDE=SCHEMA:"='HR'"
    How about
    EXCLUDE=SCHEMA:"IN ('HR', 'SCOTT', 'BLAKE')"
    Dean

  • How to exclude a schema in imp & imp error

    Hi Folks,
    Is there a way to exculde a schema when using full=y in imp (import).
    Why i prefer this is because im getting the below error while importing the dumpfile
    "ALTER SESSION SET CURRENT_SCHEMA= "PERFSTAT""
    IMP-00003: ORACLE error 1435 encountered
    ORA-01435: user does not exist
    IMP-00000: Import terminated unsuccessfully
    since I dont have (dont want) perfstat in my destination database, I want to exculde perfstat schema during import.
    Also, I dont perfer to go fromuser touser, since some pubic synonym/objects misses.
    Regards
    KSG
    Edited by: KSG on Aug 30, 2011 7:13 PM

    Ok. You can perform schema level import with imp by using FROMUSER parameter.
    User (Owner)--allows you to import all objects that belong to you (such as tables, grants, indexes, and procedures). A privileged user importing in user mode can import all objects in the schemas of a specified set of users. Use the FROMUSER parameter to specify this mode.
    Source:http://download.oracle.com/docs/cd/B10501_01/server.920/a96652/ch02.htm#1005111
    But, your question is you wish to exclude one or more schema from a full=y exported dump, then it is not possible with imp, because there is no EXCLUDE parameter with imp, but you can use FROMUSER to get import from export dump.
    Regards
    Girish Sharma

  • INCLUDE & EXCLUDE in Data Pump

    Any reason why DATA PUMP does not allow INCLUDE parameter when you have the EXCLUDE parameter in your statement and vice versa?

    "Data Pump offers much greater metadata filtering than original Export and Import. The INCLUDE parameter allows you to specify which object (and its dependent objects) you want to keep in the export job. The EXCLUDE parameter allows you to specify which object (and its dependent objects) you want to keep out of the export job. You cannot mix the two parameters in one job. Both parameters work with Data Pump Import as well, and you can use different INCLUDE and EXCLUDE options for different operations on the same dump file."
    Source: http://www.oracle.com/technology/products/database/utilities/pdf/datapump11g2007_quickstart.pdf
    Jonathan Ferreira
    http://oracle4dbas.blogspot.com

  • Exclude tables list kink option in exp/imp ????

    Hi,
    Is there any option to exclude tables while exp/imp, if so from which version?
    Thanks.

    Actually, in 10.1 and later, the Data Pump versions of export and import allow you to specify an EXClUDE parameter to exclude one or more tables.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Unable to create a schedule to exclude days and interval within each day

    Please can someone help me with this issue:
    I'm trying to create a schedule to run job every 10 mins from Monday 8am -Until Saturday 10am. Which means not to run run it from (sat 8am-Mon 10am).
    I know you can can use "exclude" parameter but some how I can get to work:
    I'm trying to do this:
    EGIN
    DBMS_SCHEDULER.create_schedule (schedule_name => 'sat10am_onward'
    ,start_date => SYSTIMESTAMP
    ,repeat_interval => 'freq=hourly;byday=sat;byhour=10,11,12,13,14,15,16,17,18,19,20,21,22,23;'
    ,comments => 'sat10am_onward'
    END;
    BEGIN
    DBMS_SCHEDULER.create_schedule (schedule_name => 'all_sunday'
    ,start_date => SYSTIMESTAMP
    ,repeat_interval => 'freq=hourly;byday=sun;byhour=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23;'
    ,comments => 'all_sunday'
    END;
    BEGIN
    DBMS_SCHEDULER.create_schedule (schedule_name => 'monday_TO_8'
    ,start_date => SYSTIMESTAMP
    ,repeat_interval => 'freq=hourly;byday=mon;byhour=0,1,2,3,4,5,6,7;'
    ,comments => 'monday_to_8'
    END;
    BEGIN
    DBMS_SCHEDULER.create_schedule (schedule_name => 'Mon_fri_10_min_not_sat10_mon8'
    ,start_date => SYSTIMESTAMP
    ,repeat_interval => 'freq=minutely;interval=10; exclude=all_sunday;exclude=monday_TO_8;exclude=sat10am_onward;'
    ,comments => 'Mon_fri_10_min_not_sat10_mon8'
    END;
    I exlude three other schedulers but I get an error?
    Does any one know what would be the best way to create this type of schedules?
    Thanks
    Xhev-

    Hi Bruce,
    Presenter 9.0 will require a new packager to create the installation package. We can provide details about the new packager in mail. Pls. write to me [email protected] and provide the following details:-
    1. Windows version where Presenter will be installed
    2. Powerpoint version (Office 2010 or Office 2013)
    3. office 32-bit or 64-bit
    Thanks,
    Jayashree
    Adobe Presenter Engg. Team

  • Script to download source packages

    Hi there,
    I've made a Bash script "getsrc.sh" which download easily and quickly source packages from AUR or ABS (dependencies : yaourt and makepkg). The idea is just to do in one command, something we usually do in several commands (I use yaourt -G, then makepkg -o). Example :
    /home/ehmicky $ getsrc gnome-terminal
    /tmp/gnome-terminal/src/gnome-terminal-3.2.1 $ ls
    aclocal.m4 AUTHORS ChangeLog ChangeLog.pre-2-23 ChangeLog.README config.guess
    config.h.in config.sub configure configure.ac COPYING depcomp
    gnome-doc-utils.make gnome-terminal.desktop.in.in HACKING help install-sh ltmain.sh
    Makefile.am Makefile.in missing mkinstalldirs NEWS omf.make
    po README src xmldocs.make
    It's just a Bash script you need to source in your ~/.bashrc if you want to use :
    source /path/to/getsrc.sh
    I didn't package it cause I'm new to Archlinux and still uncomfortable with the packaging procedure right now.
    I'm really not sure this might be useful for anyone (it might probably be useless indeed). I guess there are already alternatives doing just the same thign, but since while googling for it, I didn't bump into them, I thought I could post this script just in case.
    Do getsrc -h for usage.
    Here is the script file :
    #!/bin/bash
    #============================================================================
    # NAME : getsrc
    # DESCRIPTION : Download source packages from ABS or AUR.
    # AUTHOR AND COPYRIGHT : ehmicky <ehmickyy at hotmail dot fr>
    # LICENSE : GPL3, see end of file
    # DEPENDENCIES : yaourt makepkg
    # USAGE : getsrc PACKAGE_NAME...
    # INSTALLATION : this file needs to be sourced (e.g. "source
    # getsrc.sh") in your ~/.bashrc
    # VARIABLES :
    # SourceDir : directory where to download the source package (default :
    # current directory)
    # VERSION : 1.1 (13/03/2012)
    # CHANGELOG : 1.1
    # * Supressed output
    # * Fix getopts bug
    # 1.0
    # * First release
    #============================================================================
    #Must define a function so it doesn't spawn a new subshell, and so we can
    #change the current directory of the caller
    getsrc()
    #Define this variable to change the download directory for source packages
    #(default is the current directory)
    local SourceDir="/tmp/MyTemp"
    #Verify dependencies
    test_command()
    while (( $# ))
    do
    if ! type "$1" &> /dev/null
    then
    echo "Error: $1 is not installed." >&2
    return 1
    fi
    shift
    done
    test_command yaourt makepkg
    #Script options : see help message for more info
    local makepkg_options="#"
    OPTIND=1
    while getopts ":hr" Opt
    do
    case "$Opt" in
    h)
    echo "getsrc: Download source packages from ABS or AUR
    Usage: $0 [OPTION]... PACKAGE_NAME...
    -r Use this option if you're root.
    -h Prints this help message.
    E-mail bug reports to: <ehmickyy at hotmail dot fr>"
    return ;;
    r)
    local makepkg_options="--asroot" ;;
    echo "Error: -$OPTARG is not a valid option." >&2
    return 1 ;;
    esac
    done
    shift $(( OPTIND - 1 ))
    local _SourceDir="${SourceDir:-.}"
    if [[ $UID -eq 0 && "$makepkg_options" != *"--asroot"* ]]
    then
    echo "Error: when root, please use the -r flag." >&2
    return 1
    fi
    #Process every argument from command line
    while (( $# ))
    do
    local PreviousDir="$PWD"
    #Go in the source package download directory
    [[ -d "$_SourceDir" ]]\
    || mkdir -p "$_SourceDir"
    if [[ ! -d "$_SourceDir" ]]
    then
    echo "Error: cannot create directory $_SourceDir" >&2
    cd "$PreviousDir"
    return 1
    fi
    cd "$_SourceDir"
    #Download the ABS of the package
    yaourt -G "$1" > /dev/null 2>&1
    #Check is the ABS has been downloaded
    if [[ ! -d "$1" ]]
    then
    echo "Error: $1 is not a valid package name" >&2
    local RelatedPackages="$( yaourt --color -Ss "$1"\
    | sed -n 'h;n;p;g;p'\
    | tac) "
    [[ "$RelatedPackages" =~ ^\ *$ ]]\
    || echo -e "Maybe you meant:\n$RelatedPackages" >&2
    cd "$PreviousDir"
    return 1
    fi
    #Download the source package from the ABS
    cd "$1"
    if ! makepkg -o "$makepkg_options" > /dev/null 2>&1
    then
    echo "Error: could not download source package" >&2
    rm -r "$_SourceDir/$1"
    cd "$PreviousDir"
    return 1
    fi
    #Goes to the root of the source package
    [[ -d "src/" ]]\
    || return
    cd "src/"
    local FinalSourceDir="$( find -mindepth 1 -maxdepth 1 -type d )"
    [[ -d "$FinalSourceDir" ]]\
    && cd "$FinalSourceDir"
    #Process next argument
    shift
    done
    # GNU GENERAL PUBLIC LICENSE
    # Version 3, 29 June 2007
    # Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
    # Everyone is permitted to copy and distribute verbatim copies
    # of this license document, but changing it is not allowed.
    # Preamble
    # The GNU General Public License is a free, copyleft license for
    # software and other kinds of works.
    # The licenses for most software and other practical works are designed
    # to take away your freedom to share and change the works. By contrast,
    # the GNU General Public License is intended to guarantee your freedom to
    # share and change all versions of a program--to make sure it remains free
    # software for all its users. We, the Free Software Foundation, use the
    # GNU General Public License for most of our software; it applies also to
    # any other work released this way by its authors. You can apply it to
    # your programs, too.
    # When we speak of free software, we are referring to freedom, not
    # price. Our General Public Licenses are designed to make sure that you
    # have the freedom to distribute copies of free software (and charge for
    # them if you wish), that you receive source code or can get it if you
    # want it, that you can change the software or use pieces of it in new
    # free programs, and that you know you can do these things.
    # To protect your rights, we need to prevent others from denying you
    # these rights or asking you to surrender the rights. Therefore, you have
    # certain responsibilities if you distribute copies of the software, or if
    # you modify it: responsibilities to respect the freedom of others.
    # For example, if you distribute copies of such a program, whether
    # gratis or for a fee, you must pass on to the recipients the same
    # freedoms that you received. You must make sure that they, too, receive
    # or can get the source code. And you must show them these terms so they
    # know their rights.
    # Developers that use the GNU GPL protect your rights with two steps:
    # (1) assert copyright on the software, and (2) offer you this License
    # giving you legal permission to copy, distribute and/or modify it.
    # For the developers' and authors' protection, the GPL clearly explains
    # that there is no warranty for this free software. For both users' and
    # authors' sake, the GPL requires that modified versions be marked as
    # changed, so that their problems will not be attributed erroneously to
    # authors of previous versions.
    # Some devices are designed to deny users access to install or run
    # modified versions of the software inside them, although the manufacturer
    # can do so. This is fundamentally incompatible with the aim of
    # protecting users' freedom to change the software. The systematic
    # pattern of such abuse occurs in the area of products for individuals to
    # use, which is precisely where it is most unacceptable. Therefore, we
    # have designed this version of the GPL to prohibit the practice for those
    # products. If such problems arise substantially in other domains, we
    # stand ready to extend this provision to those domains in future versions
    # of the GPL, as needed to protect the freedom of users.
    # Finally, every program is threatened constantly by software patents.
    # States should not allow patents to restrict development and use of
    # software on general-purpose computers, but in those that do, we wish to
    # avoid the special danger that patents applied to a free program could
    # make it effectively proprietary. To prevent this, the GPL assures that
    # patents cannot be used to render the program non-free.
    # The precise terms and conditions for copying, distribution and
    # modification follow.
    # TERMS AND CONDITIONS
    # 0. Definitions.
    # "This License" refers to version 3 of the GNU General Public License.
    # "Copyright" also means copyright-like laws that apply to other kinds of
    # works, such as semiconductor masks.
    # "The Program" refers to any copyrightable work licensed under this
    # License. Each licensee is addressed as "you". "Licensees" and
    # "recipients" may be individuals or organizations.
    # To "modify" a work means to copy from or adapt all or part of the work
    # in a fashion requiring copyright permission, other than the making of an
    # exact copy. The resulting work is called a "modified version" of the
    # earlier work or a work "based on" the earlier work.
    # A "covered work" means either the unmodified Program or a work based
    # on the Program.
    # To "propagate" a work means to do anything with it that, without
    # permission, would make you directly or secondarily liable for
    # infringement under applicable copyright law, except executing it on a
    # computer or modifying a private copy. Propagation includes copying,
    # distribution (with or without modification), making available to the
    # public, and in some countries other activities as well.
    # To "convey" a work means any kind of propagation that enables other
    # parties to make or receive copies. Mere interaction with a user through
    # a computer network, with no transfer of a copy, is not conveying.
    # An interactive user interface displays "Appropriate Legal Notices"
    # to the extent that it includes a convenient and prominently visible
    # feature that (1) displays an appropriate copyright notice, and (2)
    # tells the user that there is no warranty for the work (except to the
    # extent that warranties are provided), that licensees may convey the
    # work under this License, and how to view a copy of this License. If
    # the interface presents a list of user commands or options, such as a
    # menu, a prominent item in the list meets this criterion.
    # 1. Source Code.
    # The "source code" for a work means the preferred form of the work
    # for making modifications to it. "Object code" means any non-source
    # form of a work.
    # A "Standard Interface" means an interface that either is an official
    # standard defined by a recognized standards body, or, in the case of
    # interfaces specified for a particular programming language, one that
    # is widely used among developers working in that language.
    # The "System Libraries" of an executable work include anything, other
    # than the work as a whole, that (a) is included in the normal form of
    # packaging a Major Component, but which is not part of that Major
    # Component, and (b) serves only to enable use of the work with that
    # Major Component, or to implement a Standard Interface for which an
    # implementation is available to the public in source code form. A
    # "Major Component", in this context, means a major essential component
    # (kernel, window system, and so on) of the specific operating system
    # (if any) on which the executable work runs, or a compiler used to
    # produce the work, or an object code interpreter used to run it.
    # The "Corresponding Source" for a work in object code form means all
    # the source code needed to generate, install, and (for an executable
    # work) run the object code and to modify the work, including scripts to
    # control those activities. However, it does not include the work's
    # System Libraries, or general-purpose tools or generally available free
    # programs which are used unmodified in performing those activities but
    # which are not part of the work. For example, Corresponding Source
    # includes interface definition files associated with source files for
    # the work, and the source code for shared libraries and dynamically
    # linked subprograms that the work is specifically designed to require,
    # such as by intimate data communication or control flow between those
    # subprograms and other parts of the work.
    # The Corresponding Source need not include anything that users
    # can regenerate automatically from other parts of the Corresponding
    # Source.
    # The Corresponding Source for a work in source code form is that
    # same work.
    # 2. Basic Permissions.
    # All rights granted under this License are granted for the term of
    # copyright on the Program, and are irrevocable provided the stated
    # conditions are met. This License explicitly affirms your unlimited
    # permission to run the unmodified Program. The output from running a
    # covered work is covered by this License only if the output, given its
    # content, constitutes a covered work. This License acknowledges your
    # rights of fair use or other equivalent, as provided by copyright law.
    # You may make, run and propagate covered works that you do not
    # convey, without conditions so long as your license otherwise remains
    # in force. You may convey covered works to others for the sole purpose
    # of having them make modifications exclusively for you, or provide you
    # with facilities for running those works, provided that you comply with
    # the terms of this License in conveying all material for which you do
    # not control copyright. Those thus making or running the covered works
    # for you must do so exclusively on your behalf, under your direction
    # and control, on terms that prohibit them from making any copies of
    # your copyrighted material outside their relationship with you.
    # Conveying under any other circumstances is permitted solely under
    # the conditions stated below. Sublicensing is not allowed; section 10
    # makes it unnecessary.
    # 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
    # No covered work shall be deemed part of an effective technological
    # measure under any applicable law fulfilling obligations under article
    # 11 of the WIPO copyright treaty adopted on 20 December 1996, or
    # similar laws prohibiting or restricting circumvention of such
    # measures.
    # When you convey a covered work, you waive any legal power to forbid
    # circumvention of technological measures to the extent such circumvention
    # is effected by exercising rights under this License with respect to
    # the covered work, and you disclaim any intention to limit operation or
    # modification of the work as a means of enforcing, against the work's
    # users, your or third parties' legal rights to forbid circumvention of
    # technological measures.
    # 4. Conveying Verbatim Copies.
    # You may convey verbatim copies of the Program's source code as you
    # receive it, in any medium, provided that you conspicuously and
    # appropriately publish on each copy an appropriate copyright notice;
    # keep intact all notices stating that this License and any
    # non-permissive terms added in accord with section 7 apply to the code;
    # keep intact all notices of the absence of any warranty; and give all
    # recipients a copy of this License along with the Program.
    # You may charge any price or no price for each copy that you convey,
    # and you may offer support or warranty protection for a fee.
    # 5. Conveying Modified Source Versions.
    # You may convey a work based on the Program, or the modifications to
    # produce it from the Program, in the form of source code under the
    # terms of section 4, provided that you also meet all of these conditions:
    # a) The work must carry prominent notices stating that you modified
    # it, and giving a relevant date.
    # b) The work must carry prominent notices stating that it is
    # released under this License and any conditions added under section
    # 7. This requirement modifies the requirement in section 4 to
    # "keep intact all notices".
    # c) You must license the entire work, as a whole, under this
    # License to anyone who comes into possession of a copy. This
    # License will therefore apply, along with any applicable section 7
    # additional terms, to the whole of the work, and all its parts,
    # regardless of how they are packaged. This License gives no
    # permission to license the work in any other way, but it does not
    # invalidate such permission if you have separately received it.
    # d) If the work has interactive user interfaces, each must display
    # Appropriate Legal Notices; however, if the Program has interactive
    # interfaces that do not display Appropriate Legal Notices, your
    # work need not make them do so.
    # A compilation of a covered work with other separate and independent
    # works, which are not by their nature extensions of the covered work,
    # and which are not combined with it such as to form a larger program,
    # in or on a volume of a storage or distribution medium, is called an
    # "aggregate" if the compilation and its resulting copyright are not
    # used to limit the access or legal rights of the compilation's users
    # beyond what the individual works permit. Inclusion of a covered work
    # in an aggregate does not cause this License to apply to the other
    # parts of the aggregate.
    # 6. Conveying Non-Source Forms.
    # You may convey a covered work in object code form under the terms
    # of sections 4 and 5, provided that you also convey the
    # machine-readable Corresponding Source under the terms of this License,
    # in one of these ways:
    # a) Convey the object code in, or embodied in, a physical product
    # (including a physical distribution medium), accompanied by the
    # Corresponding Source fixed on a durable physical medium
    # customarily used for software interchange.
    # b) Convey the object code in, or embodied in, a physical product
    # (including a physical distribution medium), accompanied by a
    # written offer, valid for at least three years and valid for as
    # long as you offer spare parts or customer support for that product
    # model, to give anyone who possesses the object code either (1) a
    # copy of the Corresponding Source for all the software in the
    # product that is covered by this License, on a durable physical
    # medium customarily used for software interchange, for a price no
    # more than your reasonable cost of physically performing this
    # conveying of source, or (2) access to copy the
    # Corresponding Source from a network server at no charge.
    # c) Convey individual copies of the object code with a copy of the
    # written offer to provide the Corresponding Source. This
    # alternative is allowed only occasionally and noncommercially, and
    # only if you received the object code with such an offer, in accord
    # with subsection 6b.
    # d) Convey the object code by offering access from a designated
    # place (gratis or for a charge), and offer equivalent access to the
    # Corresponding Source in the same way through the same place at no
    # further charge. You need not require recipients to copy the
    # Corresponding Source along with the object code. If the place to
    # copy the object code is a network server, the Corresponding Source
    # may be on a different server (operated by you or a third party)
    # that supports equivalent copying facilities, provided you maintain
    # clear directions next to the object code saying where to find the
    # Corresponding Source. Regardless of what server hosts the
    # Corresponding Source, you remain obligated to ensure that it is
    # available for as long as needed to satisfy these requirements.
    # e) Convey the object code using peer-to-peer transmission, provided
    # you inform other peers where the object code and Corresponding
    # Source of the work are being offered to the general public at no
    # charge under subsection 6d.
    # A separable portion of the object code, whose source code is excluded
    # from the Corresponding Source as a System Library, need not be
    # included in conveying the object code work.
    # A "User Product" is either (1) a "consumer product", which means any
    # tangible personal property which is normally used for personal, family,
    # or household purposes, or (2) anything designed or sold for incorporation
    # into a dwelling. In determining whether a product is a consumer product,
    # doubtful cases shall be resolved in favor of coverage. For a particular
    # product received by a particular user, "normally used" refers to a
    # typical or common use of that class of product, regardless of the status
    # of the particular user or of the way in which the particular user
    # actually uses, or expects or is expected to use, the product. A product
    # is a consumer product regardless of whether the product has substantial
    # commercial, industrial or non-consumer uses, unless such uses represent
    # the only significant mode of use of the product.
    # "Installation Information" for a User Product means any methods,
    # procedures, authorization keys, or other information required to install
    # and execute modified versions of a covered work in that User Product from
    # a modified version of its Corresponding Source. The information must
    # suffice to ensure that the continued functioning of the modified object
    # code is in no case prevented or interfered with solely because
    # modification has been made.
    # If you convey an object code work under this section in, or with, or
    # specifically for use in, a User Product, and the conveying occurs as
    # part of a transaction in which the right of possession and use of the
    # User Product is transferred to the recipient in perpetuity or for a
    # fixed term (regardless of how the transaction is characterized), the
    # Corresponding Source conveyed under this section must be accompanied
    # by the Installation Information. But this requirement does not apply
    # if neither you nor any third party retains the ability to install
    # modified object code on the User Product (for example, the work has
    # been installed in ROM).
    # The requirement to provide Installation Information does not include a
    # requirement to continue to provide support service, warranty, or updates
    # for a work that has been modified or installed by the recipient, or for
    # the User Product in which it has been modified or installed. Access to a
    # network may be denied when the modification itself materially and
    # adversely affects the operation of the network or violates the rules and
    # protocols for communication across the network.
    # Corresponding Source conveyed, and Installation Information provided,
    # in accord with this section must be in a format that is publicly
    # documented (and with an implementation available to the public in
    # source code form), and must require no special password or key for
    # unpacking, reading or copying.
    # 7. Additional Terms.
    # "Additional permissions" are terms that supplement the terms of this
    # License by making exceptions from one or more of its conditions.
    # Additional permissions that are applicable to the entire Program shall
    # be treated as though they were included in this License, to the extent
    # that they are valid under applicable law. If additional permissions
    # apply only to part of the Program, that part may be used separately
    # under those permissions, but the entire Program remains governed by
    # this License without regard to the additional permissions.
    # When you convey a copy of a covered work, you may at your option
    # remove any additional permissions from that copy, or from any part of
    # it. (Additional permissions may be written to require their own
    # removal in certain cases when you modify the work.) You may place
    # additional permissions on material, added by you to a covered work,
    # for which you have or can give appropriate copyright permission.
    # Notwithstanding any other provision of this License, for material you
    # add to a covered work, you may (if authorized by the copyright holders of
    # that material) supplement the terms of this License with terms:
    # a) Disclaiming warranty or limiting liability differently from the
    # terms of sections 15 and 16 of this License; or
    # b) Requiring preservation of specified reasonable legal notices or
    # author attributions in that material or in the Appropriate Legal
    # Notices displayed by works containing it; or
    # c) Prohibiting misrepresentation of the origin of that material, or
    # requiring that modified versions of such material be marked in
    # reasonable ways as different from the original version; or
    # d) Limiting the use for publicity purposes of names of licensors or
    # authors of the material; or
    # e) Declining to grant rights under trademark law for use of some
    # trade names, trademarks, or service marks; or
    # f) Requiring indemnification of licensors and authors of that
    # material by anyone who conveys the material (or modified versions of
    # it) with contractual assumptions of liability to the recipient, for
    # any liability that these contractual assumptions directly impose on
    # those licensors and authors.
    # All other non-permissive additional terms are considered "further
    # restrictions" within the meaning of section 10. If the Program as you
    # received it, or any part of it, contains a notice stating that it is
    # governed by this License along with a term that is a further
    # restriction, you may remove that term. If a license document contains
    # a further restriction but permits relicensing or conveying under this
    # License, you may add to a covered work material governed by the terms
    # of that license document, provided that the further restriction does
    # not survive such relicensing or conveying.
    # If you add terms to a covered work in accord with this section, you
    # must place, in the relevant source files, a statement of the
    # additional terms that apply to those files, or a notice indicating
    # where to find the applicable terms.
    # Additional terms, permissive or non-permissive, may be stated in the
    # form of a separately written license, or stated as exceptions;
    # the above requirements apply either way.
    # 8. Termination.
    # You may not propagate or modify a covered work except as expressly
    # provided under this License. Any attempt otherwise to propagate or
    # modify it is void, and will automatically terminate your rights under
    # this License (including any patent licenses granted under the third
    # paragraph of section 11).
    # However, if you cease all violation of this License, then your
    # license from a particular copyright holder is reinstated (a)
    # provisionally, unless and until the copyright holder explicitly and
    # finally terminates your license, and (b) permanently, if the copyright
    # holder fails to notify you of the violation by some reasonable means
    # prior to 60 days after the cessation.
    # Moreover, your license from a particular copyright holder is
    # reinstated permanently if the copyright holder notifies you of the
    # violation by some reasonable means, this is the first time you have
    # received notice of violation of this License (for any work) from that
    # copyright holder, and you cure the violation prior to 30 days after
    # your receipt of the notice.
    # Termination of your rights under this section does not terminate the
    # licenses of parties who have received copies or rights from you under
    # this License. If your rights have been terminated and not permanently
    # reinstated, you do not qualify to receive new licenses for the same
    # material under section 10.
    # 9. Acceptance Not Required for Having Copies.
    # You are not required to accept this License in order to receive or
    # run a copy of the Program. Ancillary propagation of a covered work
    # occurring solely as a consequence of using peer-to-peer transmission
    # to receive a copy likewise does not require acceptance. However,
    # nothing other than this License grants you permission to propagate or
    # modify any covered work. These actions infringe copyright if you do
    # not accept this License. Therefore, by modifying or propagating a
    # covered work, you indicate your acceptance of this License to do so.
    # 10. Automatic Licensing of Downstream Recipients.
    # Each time you convey a covered work, the recipient automatically
    # receives a license from the original licensors, to run, modify and
    # propagate that work, subject to this License. You are not responsible
    # for enforcing compliance by third parties with this License.
    # An "entity transaction" is a transaction transferring control of an
    # organization, or substantially all assets of one, or subdividing an
    # organization, or merging organizations. If propagation of a covered
    # work results from an entity transaction, each party to that
    # transaction who receives a copy of the work also receives whatever
    # licenses to the work the party's predecessor in interest had or could
    # give under the previous paragraph, plus a right to possession of the
    # Corresponding Source of the work from the predecessor in interest, if
    # the predecessor has it or can get it with reasonable efforts.
    # You may not impose any further restrictions on the exercise of the
    # rights granted or affirmed under this License. For example, you may
    # not impose a license fee, royalty, or other charge for exercise of
    # rights granted under this License, and you may not initiate litigation
    # (including a cross-claim or counterclaim in a lawsuit) alleging that
    # any patent claim is infringed by making, using, selling, offering for
    # sale, or importing the Program or any portion of it.
    # 11. Patents.
    # A "contributor" is a copyright holder who authorizes use under this
    # License of the Program or a work on which the Program is based. The
    # work thus licensed is called the contributor's "contributor version".
    # A contributor's "essential patent claims" are all patent claims
    # owned or controlled by the contributor, whether already acquired or
    # hereafter acquired, that would be infringed by some manner, permitted
    # by this License, of making, using, or selling its contributor version,
    # but do not include claims that would be infringed only as a
    # consequence of further modification of the contributor version. For
    # purposes of this definition, "control" includes the right to grant
    # patent sublicenses in a manner consistent with the requirements of
    # this License.
    # Each contributor grants you a non-exclusive, worldwide, royalty-free
    # patent license under the contributor's essential patent claims, to
    # make, use, sell, offer for sale, import and otherwise run, modify and
    # propagate the contents of its contributor version.
    # In the following three paragraphs, a "patent license" is any express
    # agreement or commitment, however denominated, not to enforce a patent
    # (such as an express permission to practice a patent or covenant not to
    # sue for patent infringement). To "grant" such a patent license to a
    # party means to make such an agreement or commitment not to enforce a
    # patent against the party.
    # If you convey a covered work, knowingly relying on a patent license,
    # and the Corresponding Source of the work is not available for anyone
    # to copy, free of charge and under the terms of this License, through a
    # publicly available network server or other readily accessible means,
    # then you must either (1) cause the Corresponding Source to be so
    # available, or (2) arrange to deprive yourself of the benefit of the
    # patent license for this particular work, or (3) arrange, in a manner
    # consistent with the requirements of this License, to extend the patent
    # license to downstream recipients. "Knowingly relying" means you have
    # actual knowledge that, but for the patent license, your conveying the
    # covered work in a country, or your recipient's use of the covered work
    # in a country, would infringe one or more identifiable patents in that
    # country that you have reason to believe are valid.
    # If, pursuant to or in connection with a single transaction or
    # arrangement, you convey, or propagate by procuring conveyance of, a
    # covered work, and grant a patent license to some of the parties
    # receiving the covered work authorizing them to use, propagate, modify
    # or convey a specific copy of the covered work, then the patent license
    # you grant is automatically extended to all recipients of the covered
    # work and works based on it.
    # A patent license is "discriminatory" if it does not include within
    # the scope of its coverage, prohibits the exercise of, or is
    # conditioned on the non-exercise of one or more of the rights that are
    # specifically granted under this License. You may not convey a covered
    # work if you are a party to an arrangement with a third party that is
    # in the business of distributing software, under which you make payment
    # to the third party based on the extent of your activity of conveying
    # the work, and under which the third party grants, to any of the
    # parties who would receive the covered work from you, a discriminatory
    # patent license (a) in connection with copies of the covered work
    # conveyed by you (or copies made from those copies), or (b) primarily
    # for and in connection with specific products or compilations that
    # contain the covered work, unless you entered into that arrangement,
    # or that patent license was granted, prior to 28 March 2007.
    # Nothing in this License shall be construed as excluding or limiting
    # any implied license or other defenses to infringement that may
    # otherwise be available to you under applicable patent law.
    # 12. No Surrender of Others' Freedom.
    # If conditions are imposed on you (whether by court order, agreement or
    # otherwise) that contradict the conditions of this License, they do not
    # excuse you from the conditions of this License. If you cannot convey a
    # covered work so as to satisfy simultaneously your obligations under this
    # License and any other pertinent obligations, then as a consequence you may
    # not convey it at all. For example, if you agree to terms that obligate you
    # to collect a royalty for further conveying from those to whom you convey
    # the Program, the only way you could satisfy both those terms and this
    # License would be to refrain entirely from conveying the Program.
    # 13. Use with the GNU Affero General Public License.
    # Notwithstanding any other provision of this License, you have
    # permission to link or combine any covered work with a work licensed
    # under version 3 of the GNU Affero General Public License into a single
    # combined work, and to convey the resulting work. The terms of this
    # License will continue to apply to the part which is the covered work,
    # but the special requirements of the GNU Affero General Public License,
    # section 13, concerning interaction through a network will apply to the
    # combination as such.
    # 14. Revised Versions of this License.
    # The Free Software Foundation may publish revised and/or new versions of
    # the GNU General Public License from time to time. Such new versions will
    # be similar in spirit to the present version, but may differ in detail to
    # address new problems or concerns.
    # Each version is given a distinguishing version number. If the
    # Program specifies that a certain numbered version of the GNU General
    # Public License "or any later version" applies to it, you have the
    # option of following the terms and conditions either of that numbered
    # version or of any later version published by the Free Software
    # Foundation. If the Program does not specify a version number of the
    # GNU General Public License, you may choose any version ever published
    # by the Free Software Foundation.
    # If the Program specifies that a proxy can decide which future
    # versions of the GNU General Public License can be used, that proxy's
    # public statement of acceptance of a version permanently authorizes you
    # to choose that version for the Program.
    # Later license versions may give you additional or different
    # permissions. However, no additional obligations are imposed on any
    # author or copyright holder as a result of your choosing to follow a
    # later version.
    # 15. Disclaimer of Warranty.
    # THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
    # APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
    # HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
    # OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
    # THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    # PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
    # IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
    # ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
    # 16. Limitation of Liability.
    # IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
    # WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
    # THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
    # GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
    # USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
    # DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
    # PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
    # EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
    # SUCH DAMAGES.
    # 17. Interpretation of Sections 15 and 16.
    # If the disclaimer of warranty and limitation of liability provided
    # above cannot be given local legal effect according to their terms,
    # reviewing courts shall apply local law that most closely approximates
    # an absolute waiver of all civil liability in connection with the
    # Program, unless a warranty or assumption of liability accompanies a
    # copy of the Program in return for a fee.
    # END OF TERMS AND CONDITIONS
    # How to Apply These Terms to Your New Programs
    # If you develop a new program, and you want it to be of the greatest
    # possible use to the public, the best way to achieve this is to make it
    # free software which everyone can redistribute and change under these terms.
    # To do so, attach the following notices to the program. It is safest
    # to attach them to the start of each source file to most effectively
    # state the exclusion of warranty; and each file should have at least
    # the "copyright" line and a pointer to where the full notice is found.
    # <one line to give the program's name and a brief idea of what it does.>
    # Copyright (C) <year> <name of author>
    # This program is free software: you can redistribute it and/or modify
    # it under the terms of the GNU General Public License as published by
    # the Free Software Foundation, either version 3 of the License, or
    # (at your option) any later version.
    # This program is distributed in the hope that it will be useful,
    # but WITHOUT ANY WARRANTY; without even the implied warranty of
    # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    # GNU General Public License for more details.
    # You should have received a copy of the GNU General Public License
    # along with this program. If not, see <http://www.gnu.org/licenses/>.
    # Also add information on how to contact you by electronic and paper mail.
    # If the program does terminal interaction, make it output a short
    # notice like this when it starts in an interactive mode:
    # <program> Copyright (C) <year> <name of author>
    # This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    # This is free software, and you are welcome to redistribute it
    # under certain conditions; type `show c' for details.
    # The hypothetical commands `show w' and `show c' should show the appropriate
    # parts of the General Public License. Of course, your program's commands
    # might be different; for a GUI interface, you would use an "about box".
    # You should also get your employer (if you work as a programmer) or school,
    # if any, to sign a "copyright disclaimer" for the program, if necessary.
    # For more information on this, and how to apply and follow the GNU GPL, see
    # <http://www.gnu.org/licenses/>.
    # The GNU General Public License does not permit incorporating your program
    # into proprietary programs. If your program is a subroutine library, you
    # may consider it more useful to permit linking proprietary applications with
    # the library. If this is what you want to do, use the GNU Lesser General
    # Public License instead of this License. But first, please read
    # <http://www.gnu.org/philosophy/why-not-lgpl.html>.
    Last edited by ehmicky (2012-03-13 20:46:18)

    Here is the output of makepkg -s when I try to install packer:
    [tilley@take-kun packer]$ makepkg -s
    ==> Determining latest git revision...
      -> Version found: 20120509
    ==> Making package: packer 20120509-1 (Wed May  9 17:27:52 CDT 2012)
    ==> Checking runtime dependencies...
    ==> Installing missing dependencies...
    resolving dependencies...
    looking for inter-conflicts...
    Targets (2): jansson-2.3-1  jshon-20111222-1
    Total Download Size:    0.04 MiB
    Total Installed Size:   0.17 MiB
    Proceed with installation? [Y/n] y
    :: Retrieving packages from community...
    jansson-2.3-1-x86_64      30.5 KiB   150K/s 00:00 [######################] 100%
    jshon-20111222-1-x86_64    9.8 KiB   806K/s 00:00 [######################] 100%
    (2/2) checking package integrity                   [######################] 100%
    (2/2) loading package files                        [######################] 100%
    (2/2) checking for file conflicts                  [######################] 100%
    (2/2) checking available disk space                [######################] 100%
    (1/2) installing jansson                           [######################] 100%
    (2/2) installing jshon                             [######################] 100%
    ==> Checking buildtime dependencies...
    ==> Retrieving Sources...
    ==> Extracting Sources...
    ==> Entering fakeroot environment...
    ==> Starting build()...
    ==> Connecting to github GIT server....
    Cloning into 'packer'...
    error: Could not resolve host: (nil); No address associated with hostname while accessing https://github.com/bruenig/packer.git/info/refs
    fatal: HTTP request failed
    ==> ERROR: A failure occurred in build().
        Aborting...

  • Report model - number of values selected in DDL param

    Good afternoon,
    I have created a report model that references Teradata views, and I am using this model to populate several datasets in a Report Builder report.  One dataset returns actual results, and the other datasets are used to populate available values for multivalued
    parameters.
    The issue I'm encountering is that some of my parameters return a large number (tens or hundreds of thousands) of selectable values.  When clicking "select all", I'm getting an error, since the concatenated list of values exceeds
    the length limit.  However, since I'm working with a report model, I cannot use T-SQL workarounds such as custom "<ALL>" values/handling.  I also need to limit my result set using these values as parameters, not filters, since I want
    the intensive processing handled in the DB server, not the app server.
    Is there any possible way to accommodate this?  As an example, I have a large (200k+) list of products, belonging to about 7,000 brands.  I want both my product number and brand lists as multivalue parameters...I might want to run
    the report for all products and all brands (returning 200k+ rows), or choose "select all" in the products list, but only pick a few brands (or vice versa).  Cascading parameters (with the first parameter limiting the next set of values)
    is not an option since there are many of these parameters that have too many values for the allowed limit (i.e. even my brand list generated the error when I choose "select all" and only picked a few products).
    I have searched literally dozens of forums and tech sites, all to no avail thus far.  Any assistance will be greatly appreciated...thank you!
    -Chris

    I have a SSRS Report with 4 multi-select parameters.
    The customer has requested that they would like the drill-through to open in a new window.
    I am using Java Script for that purpose.
    However, there is a limit on how long a URL may be.
    Is there a way in a SSRS report to limit the number of values in a multi-select parameter selected?
    Thanks.
    One workaround is to add a internal parameter which will count the number of selected values and will allow the navigation only if the count falls below the threshold.
    For this you can use an expression like below for setting the internal parameter
    Len(Join(Parameters!MultiValuedParameter.Value,","))-Replace(Join(Parameters!MultiValuedParameter.Value,","),",","")
    Then use expression like below for the jump to url/report property
    IIf(Val(Parameters!HiddenParameter.Value)<=<your thresholdvalue>,<report url>,Nothing)
    You can also add a notification textbox on top which will show a message like "Report navigation not possible due to too many values selected" and keep it hidden by default. Then based on above parameter value you can make it visible
    ie make hidden property like below
    IIf(Val(Parameters!HiddenParameter.Value)<=<your thresholdvalue>,False,True)
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • EXPORT/IMPORT TABLE DATA FROM ONE SCHEMA TO ANOTHER ONE (S.O.S)

    Hi,
    I urgently need your help:(, I have two different instances, in each of them there are two schemas, A and B; which tables are the same, but I need to transfer JUST the table data from A's tables to B's tables, how can I do so??
    Thanks in advance,
    Isabel

    The total number of tables is 989:(And how many do you want ? If 988, and if you're on a 10g db, you can use exclude parameter from expdp/impdp?
    Nicolas.

  • When will file transfer be used to send a message?

    Hi,
    My understanding is that a message is only sent via file transfer if the size of the message is greater than 75% of the IPC queue capacity; file transfer will never be used in response to a blocking situation that arises due to the number of messages exhausting the queue capacity (this will result in an immediate failure if the TPNOBLOCK flag is used, or else a failure response when the timeout is reached).
    We have the following message in the ULOG:
    "TMQUEUE.4288.3081606848.0: LIBTUX_CAT:1285: WARN: tpreturn message send blocked, will try file transfer"
    Would I be correct in assuming this is because of the size of the message, or is this something specific to TMQUEUE operations? If my understanding of how transfer by disk can occur is wrong, please set me straight!
    Thanks,
    Malcolm.

    Malcolm,
    Tuxedo will use file transfer if
    a) The size of the message is greater than 75% of the total capacity of the queue.
    b) The original msgsnd() fails with EINVAL. (Some operating systems have a MSGMAX kernel configuration parameter limiting the size of an individual message which can be set to less than the total capacity of the queue. If an application attempts to send a message greater than this size it will fail with EINVAL.)
    c) The original non-blocking msgsnd() fails with EAGAIN and the message is being sent by tpreturn(). (This is the case where LIBTUX_CAT:1285 is logged.)
    d) The original non-blocking msgsnd() fails with EAGAIN, the TPNOBLOCK option is not set, the original message is over 500 bytes, the TMNOTHREADS environment variable is not set to Y, and the message is not being sent by certain system processes that are always single threaded.
    For domain gateways only, the file transfer in case (c) can be avoided if GW_FILETRANSFER=OFF is set.
    Regards,
    Ed

  • Need help on access of network settings on apple tv 2

    Hi , can anyone tell me how to fix my apple tv, the remote will let me move across to general , but I can not access any of the following to change info , eg  can not access network , itune store , etc...I unpaired the remote and repaired it 3 times , did hard boot and boot from remote , still not working .
    Can anyone suggest a fix please ..thanks Steven

    Hello,
    EXCLUDE=SCHEMA:"IN ('SYS','SYSTEM','OUTLN','PS','SYSADM','DBSNMP','PEOPLE','DIP','ORACLE_OCM','CSMIG','PSMON','PERFSTAT'"It seems that it lacks the right parenthesis on the above syntax.
    According to the Note *1133013.1* of My Oracle Support, a wrong syntax of the EXCLUDE parameter may cause the error ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS* if you use IMPDB with a Network Link.
    So you may correct the EXCLUDE parameter and try again.
    Hope this help.
    Best regards,
    Jean-Valentin

Maybe you are looking for