Pre-compiled Solaris 10 X*^ mod_jk package

Anyone knows where can I get mod_jk Solaris 10 X86 package (not the source code!)?
Thanks, Oren

The only thing I can really suggest is to scan your log files to see if the building of this object failed earlier on.
Thanks
Prashanth

Similar Messages

Solaris 10 x86 mod_jk for Apache to Tomcat compilation error

Hi,
I try to figure it out how to compile the sources of mod_jk under Solaris 10 x86 on v20z server. The configuration goes right. But when I try to use make. This error appears. The version of mod_jk is 1.1.14. Can anybody help with this probleme?
Here is the result of the make:
gcc: .libs/mod_jk.o: No such file or directory
gcc: ../common/.libs/jk_ajp12_worker.o: No such file or directory
gcc: ../common/.libs/jk_connect.o: No such file or directory
gcc: ../common/.libs/jk_msg_buff.o: No such file or directory
gcc: ../common/.libs/jk_util.o: No such file or directory
gcc: ../common/.libs/jk_ajp13.o: No such file or directory
gcc: ../common/.libs/jk_pool.o: No such file or directory
gcc: ../common/.libs/jk_worker.o: No such file or directory
gcc: ../common/.libs/jk_ajp13_worker.o: No such file or directory
gcc: ../common/.libs/jk_lb_worker.o: No such file or directory
gcc: ../common/.libs/jk_sockbuf.o: No such file or directory
gcc: ../common/.libs/jk_map.o: No such file or directory
gcc: ../common/.libs/jk_uri_worker_map.o: No such file or directory
gcc: ../common/.libs/jk_ajp14.o: No such file or directory
gcc: ../common/.libs/jk_ajp14_worker.o: No such file or directory
gcc: ../common/.libs/jk_md5.o: No such file or directory
gcc: ../common/.libs/jk_shm.o: No such file or directory
gcc: ../common/.libs/jk_ajp_common.o: No such file or directory
gcc: ../common/.libs/jk_context.o: No such file or directory
gcc: ../common/.libs/jk_status.o: No such file or directory
make[1]: *** [mod_jk.la] Error 1
make[1]: Leaving directory `/install/jakarta-tomcat-connectors-1.2.14.1-src/jk/native/apache-1.3'
make: *** [all-recursive] Error 1
Anybody can help???

You have to run "make clean" and then make.
Probably the files could not be compiled because of errors in the first place.
Try to download the source for apache and compile it for the current platform, otherwise you could get wrong settings.

Auto deploy pre-compiled JSP

Hello
In the post of gadegaard in november 2002, there was a problem to au deploy pre-compiled JSP. Is this problem has been fix in the 9.0.4 OC4J version ?
If yes, is it sufficient to create a "_pages" directory in the war (the war is contained in an ear) and auto deploy it ? Because my pre-compiled JSP are not deployed.
Tanks in advance for your answer
Emmanuelle

Emmanuelle:
There are two ways to use the precomiled JSP files.
Method one: You can just copy the generated JSP page implementation classes to the directory application-deployments/yourApp/yourWebApp/persistence/_pages. If the init-param "main_mode" of jsp servlet of your web app is reload, then these classes will be used without stopping the server. This is the fastest way in development.
Method two: You can packaged the generated JSP page implementation classes into a jar just like any other java class libraries. Then create your war with that jar inside WEB-INF/lib. Make sure the init-param "main_mode" of jsp servlet in your web.xml is justrun. Now you have a deployable war file. You can deploy the war file (within an ear file) to oc4j and access the JSP page.
Please tell me if either of thse methods works for you
Please note since oc4j 10.1.3, ojspc will package the generated classes into a jar under WEB-INF/lib if given an war or ear file.

Pre-Compiled JSPs.

Hi Gurus,
          The weblogic compiles the JSP pages, the package names of the servlets
          generated contains the directory structure along with the package prefix.
          i.e . if the jsp file calles myfile.jsp is in
          public_html/cm/log/myfile.jsp
          the servlet class generated with package
          <package_prefix>._cm._log.myfile.class in
          public_html/<package_prefix>/_cm/_log/ directory.
          If the JSPs are compiled from command line , using "java weblogic.jspc
          ... " it does not generate the "_cm._log..." package prefix.
          Right now I want to write a script to pre-compile all the JSPs after
          deployement.
          Thanks in Advance and Regards
          Arun


Hi,
          Try to use the -package option with weblogic.jspc.
          Best Regards
          Li Zhongling (Alex)
          Carpe Diem, Seize the Day !!
          Arun Kumar wrote:
          > Hi Gurus,
          > The weblogic compiles the JSP pages, the package names of the servlets
          > generated contains the directory structure along with the package prefix.
          >
          > i.e . if the jsp file calles myfile.jsp is in
          > public_html/cm/log/myfile.jsp
          > the servlet class generated with package
          > <package_prefix>._cm._log.myfile.class in
          > public_html/<package_prefix>/_cm/_log/ directory.
          >
          > If the JSPs are compiled from command line , using "java weblogic.jspc
          > ... " it does not generate the "_cm._log..." package prefix.
          > Right now I want to write a script to pre-compile all the JSPs after
          > deployement.
          >
          > Thanks in Advance and Regards
          > Arun

How to pre-compile jsp and deploy to tomcat

Hi All,
I wuld like to know how to pre-compile JSPs and deploy to tomcat. I am using ANT tool to build and deploy the war file.
Thanks in Advance.
Regards,
--Nagesh.

for Tomcat 5.0 (You'll need to edit to fit your needs)
    <path id="jsp.classpath">
        
        <fileset dir="C:\tomcat\common\lib">
            <include name="**/*.jar"/>
        </fileset>
        <fileset dir="C:/tomcat/common/endorsed">
            <include name="**/*.jar"/>
        </fileset>
    </path>
    <target name="jsp" >
    
    <taskdef name="jspc50" classname="org.apache.jasper.JspC">
        <classpath>
                <path refid="jsp.classpath"/>
        </classpath>
    </taskdef>
    <jspc50 outputDir="${build.classes}"
            package="jsp"
            uriroot="${project.dir}/web/webApp"
            webXmlFragment="c:/web.xml"
            verbose="9"
            validateXml="false">
    </jspc50>
    <javac srcdir="${build.classes}/jsp"
           destdir="${build.classes}"
           debug="true"
           optimize="false"
           includes="**/*.java"
           source="1.4">
            <classpath>
                <path refid="classpath"/>
                <path refid="jsp.classpath"/>
            </classpath>
    </javac>
</target>    More information can be found here :
http://www.onjava.com/pub/a/onjava/excerpt/AntTDG_chap8/index1.html?page=last

Pre-compiled JSPs not being recognized (WLS 8.1 SP2)

          We're running into a strange problem here, where our pre-compiled JSPs (precompiled
          via an ant target) are being recognized as "stale" and recompiled by Weblogic,
          as the following log message indicates. The strange thing is, on one hand it says
          they were precompiled by a "different" version of Weblogic server, and then right
          after that, immediately contradicts itself by logging the SAME version for the
          JSP and WLS builds:
          ####<Jan 31, 2004 11:24:40 AM PST> <Info> <HTTP> <ladybug> <fwmharris-ms01> <ExecuteThread:
          '11' for
          queue: 'default'> <dhecking> <> <BEA-101295> <Recompiling JSP
          [ServletContext(id=20425572,name=fwmhis-www,context-path=)], resource
          [tiles/table/td_twisty_group_tile.jsp], because it is stale. It was previously
          compiled using a
          different version of WebLogic Server.
          JSP build version: 8.1.2.0
          WLS build version: 8.1.2.0.>
          As can be seen, the two build versions are identical (8.1.2.0) which is the correct
          version (Weblogic 8.1 SP2). Has anyone else run into this problem? If so, is there
          a fix?
          The platform is Solaris btw.
          Thank you.
          ..Hrishi
          Hrishi Dixit
          Finaplex
          [email protected]


Kostas Symeonidis wrote:
          > I have exactly the same problem with 8.1sp2 on Win2000 and I will test it tomorrow on Solaris.
          >
          > It seems that the code checks two things:
          > 1. the version of the JSPC
          > 2. the timestamp of the files
          > In both cases the logged message is the same(!!!) "recompiling because is stale..." but you can see that clearly the version numbers are the same, therefore the stale check failed on step 2.
          >
          > Now my guess is that step 2, either doesn't find the page, or the time check is done erratically. Mind you, in 8.1sp2 BEA changed the isResourceStale method signature and added an extra String parameter for the TimeZone, see code in generated JSPs below:
          > public boolean _isStale() {
          > weblogic.servlet.jsp.StaleChecker sci =(weblogic.servlet.jsp.StaleChecker)(getServletConfig().getServletContext());
          > java.io.File f = null;
          > long lastModWhenBuilt = 0L;
          > if (sci.isResourceStale("/index.jsp", 1082047780159L, "8.1.2.0", "Europe/London")) return true;
          > return false;
          > }
          >
          > I'm also quite sure that we should be waiting for a rolling patch quite soon.
          Your guess is correct. Unfortunately a the message logged is wrong. A
          patch for CR133453 fixes that. Basically its failing (2) and logging the
          same message as (1).

Pre-compile jsp in Weblogic

Hello all,
          I have been trying to add following tags in weblogic.xml to precompile my all jsps at Deployment time, but it gives me error as follows. [I am pasting messages from the console....]
          I am using WL express 7.0 and jdk1.3 that comes along with the server.
          Here is my tag:
          <jsp-descriptor>
               <jsp-param>
                    <param-name>precompile</param-name>
          <param-value>true</param-value>
               </jsp-param>
          </jsp-descriptor>
          What is the wrong here ? Is there any special configuration in weblogic server that I am ignoring here ?
          =======================================
          <Nov 9, 2004 9:33:32 AM EST> <Debug> <HTTP> <101211> <ppdm:jsp Precompiling JSPs at startup with JSP config [JspConfig: verbose=true,package
          Prefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\user_projects\icmgdomain\.\icmgone\.wlnotdelete\icmgone_ppdm_jsp,pageChec
          kSeconds=1,superclass=weblogic.servlet.jsp.JspBase,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,
          defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false,debugEnabled=false,printNulls=true]>
          log4j:WARN No appenders could be found for logger (org.apache.struts.util.MessageResourcesFactory).
          log4j:WARN Please initialize the log4j system properly.
          <Nov 9, 2004 9:33:52 AM EST> <Error> <Deployer> <149233> <Unexpected error was encountered during the deployment process.>
          <Nov 9, 2004 9:33:52 AM EST> <Error> <Deployer> <149201> <The Slave Deployer failed to complete the deployment task with id 11 for the appli
          cation ppdm.
          java.lang.ExceptionInInitializerError: java.lang.NullPointerException
          at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
          at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
          at java.lang.Class.forName0(Native Method)

          And make sure you don't have any other patches installed!
          The generated servlet specifically checks to make sure that the servlet is running
          on the same EXACT setup (service pack, patches, etc.) that was used to generate
          it from the original JSP.
          Tim
          "Eric Ma" <[email protected]> wrote:
          >
          >Upgrade to WebLogic 6.1 SP3.
          >
          >Eric Ma
          >
          >Charley Chu <[email protected]> wrote:
          >>Did you figure out how to do it?
          >>
          >>I use weblogic.jspc in the Ant script to compile all my JSP and target
          >>the output to the WEB-INF\classes directory. Package the app into war
          >>and ear. But the server still generates the class for jsp when the jsp
          >>page is accessed on the first time.
          >>
          >>I could use deployment descriptor in weblogic.xml to pre-compile jsp
          >>when the server starts but I'd rather do it in Ant script.
          >>
          >>Any hint?
          >>
          >>Thanks!
          >

Help with JSP pre-compiling

We have a web application using Jboss4.0.5, jdk 1.6 and And 1.6.5, and now we try to do a pre-compiling as part of our build procedure.
That is the first time I am going to do a pre-comp of a major application, which includes about 1700 jsp files.
The directory tree of the application is as follows:
/project
    |--- > /web_pre-comp/pages/jsp ( it contains all the jsp files )
    |----> /web_pre-comp/WEB-INF ( it contains the web.xml file.)
    |----> /web_pre-comp/WEB-INF/tld ( it contains the tld files)
    |----> /web_pre-comp/WEB-INF/src ( it coutains the generated src file from jsp )
    |---->/web_pre-comp/WEB-INF/classes ( it contains the compiled classes once the jsp java files are generated.   )
    |----> build.xml ( the ant script )And there is my build.xml file looks like:
<project>
      <target name="pro.jsp.generate" depens="init">
       <java classname="org.apache.jasper.JspC" fork="yes">
          <classpath refid="tomcat.jsp.classpath"/>
          <arg line=" -d "/>
          <arg value="${jsp.generated.src.dir}"/>
          <arg line="-p"/>
          <arg value="${jsp.package.name}"/>
          <arg line="-webapp"/>
          <arg value="${jsp.src.dir}"/>
       </java>
   </target>
</project>When I was running the ant script, I received such message:
[java] org.apache.jasper.JasperException: The absolute uri: http://www.prounlimited.com/wandappconfig.tld cannot be resolved in either web.xml or the jar files deployed with this application
We do have suh messages included in the web.xml file.
<taglib>
        <taglib-uri>http://www.prounlimited.com/wandappconfig.tld</taglib-uri>
        <taglib-location>/WEB-INF/tld/wandappconfig.tld</taglib-location>
    </taglib>Any Ideas how to make it working ?
Another side questions is when some java file are created from JSP, I see some "005f" included in the java file name, such as "inc_sup_princing_view.jsp" creats a
"inc_005fsup_005fpricing_005fview_jsp.java" file. Does someone know why this happen ?
Thanks a lot !
Charlie

We have a web application using Jboss4.0.5, jdk 1.6
and And 1.6.5, and now we try to do a pre-compiling
as part of our build procedure. Hi Charlie,
According to your ant build script you're using Jasper compiler, but your web container is JBoss.
I know that Tomcat uses the Jasper compiler --- but I don't know if JBoss supports Jasper or not. Please check with JBoss if they support Jasper, if not they my support a different pre-compiler.
That is the first time I am going to do a pre-comp of
a major application, which includes about 1700 jsp
files.
The directory tree of the application is as follows:
/project
|--- > /web_pre-comp/pages/jsp ( it contains all
the jsp files )
|----> /web_pre-comp/WEB-INF ( it contains the
web.xml file.)
|----> /web_pre-comp/WEB-INF/tld ( it contains
the tld files)
|----> /web_pre-comp/WEB-INF/src ( it coutains the
generated src file from jsp )
|---->/web_pre-comp/WEB-INF/classes ( it contains
the compiled classes once the jsp java files are
generated.   )
|----> build.xml ( the ant script )And there is my build.xml file looks like:
<project>
<target name="pro.jsp.generate" depens="init">
<java classname="org.apache.jasper.JspC"
fork="yes">
<classpath refid="tomcat.jsp.classpath"/>
<arg line=" -d "/>
<arg value="${jsp.generated.src.dir}"/>
<arg line="-p"/>
<arg value="${jsp.package.name}"/>
<arg line="-webapp"/>
<arg value="${jsp.src.dir}"/>
java>
</target>
</project>When I was running the ant script, I received such
message:
[java] org.apache.jasper.JasperException: The
absolute uri:
http://www.prounlimited.com/wandappconfig.tld cannot
be resolved in either web.xml or the jar files
deployed with this application
Check if the tld folder is visible to the classpath tomcat.jsp.classpath used inside the Ant build file.
>
We do have suh messages included in the web.xml file.
<taglib>
taglib-uri>http://www.prounlimited.com/wandappconfig.t
ld</taglib-uri>
taglib-location>/WEB-INF/tld/wandappconfig.tld</taglib
-location>
</taglib>Any Ideas how to make it working ?
Another side questions is when some java file are
created from JSP, I see some "005f" included in the
java file name, such as "inc_sup_princing_view.jsp"
creats a
"inc_005fsup_005fpricing_005fview_jsp.java" file.
Does someone know why this happen ?
The 005f is expected, it is for internal reference for the pre-compiler, nothing to worry about.
>
Thanks a lot !
Charlie

Referenced native libraries getting pre-compiled and then throwing exception

Hi I have an issue in the universal app. I am referencing Nokia.Graphics.Imaging.dll and WindowsPreview.Media.Ocr.dll in the universal app project. Everything compiles and runs on every device I tested it with. The problem is that after some time NGen kicks
in and pre-compiles my DLLs, including the native ones. These DLLs then get corrupt and next time I run the app I get BadImageFormatException due to an attempt to load the <nativelibrary>.ni.dll. Is this a bug of NGen? When I delete these <nativelibrary>.ni.dll
files the app runs again.

Hi, unfortunately, I was not able to simulate this behavior in another project so far. Here
http://uloz.to/xRShw487/precompiled-zip are NGENed files from our application (_not_working folder) and from a filter-manager sample (_working from different_app). As you can see for some reason Lumia.Imaging.ni.dll
in our app has only 796kB, while from the other app it has 1235kB.
The NGEN log file looks ok to me:
03/23/2015 15:18:24.272 [11796]: 1>    Compiling assembly C:\Program Files\WindowsApps\app\Lumia.Imaging.Managed.DLL (CLR v4.0.30319) ...
03/23/2015 15:18:24.350 [11796]: ngen returning 0x00000000
03/23/2015 15:18:25.334 [24168]: 1>    Compiling assembly C:\Program Files\WindowsApps\app\WindowsPreview.Media.Ocr.winmd (CLR v4.0.30319) ...
03/23/2015 15:18:25.365 [24168]: ngen returning 0x00000000
03/23/2015 15:18:25.444 [8036]: 1>    Compiling assembly C:\Program Files\WindowsApps\app\Lumia.Imaging.winmd (CLR v4.0.30319) ...
03/23/2015 15:18:25.725 [8036]: ngen returning 0x00000000
Once I delete Lumia.Imaging.ni.dll and WindowsPreview.Media.Ocr.ni.dll, the app starts working again. Lumia.Imaging.Managed.DLL seems to be OK and does not cause any troubles, maybe because it is managed, while both of the problematic DLLs are native already.
Hi LVolf,
>>I am referencing Nokia.Graphics.Imaging.dll and WindowsPreview.Media.Ocr.dll in the universal app project
How did you add these references in your project? Basically, the NuGet package is the easiest way, for example:
See the
NuGet documentation for all the ways you can download and install the NuGet package in your project. To install the package from within Microsoft Visual Studio, do the following:
1.In Visual Studio, select PROJECT | Manage NuGet Packages.
2.In the Online section, select nuget.org. Search for
Microsoft.Windows.Ocr.
3.Click Install.
4.Select BUILD | Configuration Manager to change the build configuration of your project from
AnyCPU to x86, x64, or ARM.
5.If Intellisense does not work after you have installed the NuGet package, unload and reload the Visual Studio project. In Solution Explorer, right-click the project and select
Unload Project. Then right-click the project again and select
Reload Project.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Pre-compile JSPs before deploying

Hi All,
what is the best way to pre-compile my JSPs and then bundle them together into
a .war file, then deploying it ???
I have like 100 jsps that i wanted to precompile and wanted to package them together
into a abc.war file, which i can further deploy to my WLS6.1 server ?
I have another instance of WLS8.1 that i wanted to do the same thing ?
can somebody please advise me something and how to do this ?
This is on Production environment.
-steve

Steve, you're correct, the output jsp .classes are insterted into the war
file if compilation is successful.
"steve" <[email protected]> wrote in message
news:404f7e99$[email protected]..
>
Hi Raja,
Thanks for your reply. does this ant task wlappc compiles the .war fileand then
repackage into the same .war file ?
am i correct ?
please advise .....thx, steve
"Raja" <[email protected]> wrote:
Both option are will work. I am using wlappc ant task to compile my war
file prior
to deployment.
<target name="appc">
<wlappc
source="C:\abc\abc.war"
/>
</target>
Coming to deployment you can either write ant task to deploy using
console.
Example
of ant task for deploying from a windows dev machine into remoteproduction
box.
Admin server need to be running for deploy to be successful.
<target name="sun-deploy">
<wldeploy action="deploy"
source="C:\projects\abc\abc.war"
name="myapp"
user="weblogic"
password="weblogic"
verbose="true"
adminurl="http://xyz:7001"
debug="true"
targets="myserver"
upload="true"
/>
</target>
"steve" <[email protected]> wrote:
Hi All,
what is the best way to pre-compile my JSPs and then bundle them
together
into
a .war file, then deploying it ???
I have like 100 jsps that i wanted to precompile and wanted to package
them together
into a abc.war file, which i can further deploy to my WLS6.1 server?
I have another instance of WLS8.1 that i wanted to do the same thing
can somebody please advise me something and how to do this ?
This is on Production environment.
-steve

Pre-Compile JSPs

I'm trying to pre-compile my JSPs before uploading my war to the app server.
I'm using JDeveloper 10.1.2 to compile my jsps into a .war file. However, when I deploy to the app server, with main_mode (When a JSP Changes) set to Do Nothing, it can't find my compiled JSPs.
The directory where the JSPs are compiled to in the war with Jdeveloper is a .jsps package under WEB-INF/classes.
Should they go elsewhere?

Welp....after some playing around, I found that if the jsps are compiled directly under WEB-INF/classes, it works great
However, I have no idea how to change JDeveloper to tell it not to put the JSPs in the .jsp package. Any ideas?

Pre-Compiling JSPs while deploying a .war file in OC4J instance

Hi,
Is there any way to inform the OC4J instance to pre-compile the jsps in a .war file, while deploying..
Thanks for your responses,
Eshwar

Click on the project.
Open the context menu (right mouse button).
Expand the General item in the left list.
Select the Deployment Profiles item.
Select the deployment profile you need from the right.
Follow the wizard.
--olaf

SSIS Job is getting failed with an error "0x00000005 : Failed to compiled scripts contained in the package.

Hi All. Could anyone resolve my issue.
I was created a package with an Script task written in VB.Net.
The Package was executing Successfully in BIDS.
But when i tried to exceute the same using Sql server Agent Job, Its getting Failed with the below error message
"Executed as user: Admin. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 5:12:27 PM Error: 2013-03-13 17:12:32.33
Code: 0x00000005     Source: Checking Alcon Files Checking Alcon Files     Description: Failed to compiled scripts contained in the package. Open the package in SSIS Designer and resolve the compilation errors.
End Error Error: 2013-03-13 17:12:32.33     Code: 0x00000005     Source: Checking Alcon Files Checking Alcon Files     Description: BC30179 - enum 'ScriptResults' and enum 'ScriptResults' conflict
in class 'ScriptMain'., ScriptMain.vb, 156, 22 End Error Error: 2013-03-13 17:12:32.36     Code: 0x00000005     Source: Checking Alcon Files Checking Alcon Files     Description: The binary
code for the script is not found. Please open the script in the designer by clicking Edit Script button and make sure it builds successfully. End Error Error: 2013-03-13 17:12:34.28     Code: 0x00000005
Source: Formating Excel Sheet Formating Excel Sheet     Description: Failed to compiled scripts contained in the package. Open the package in SSIS Designer and resolve the compilation errors. End Error Error: 2013-03-13 17:12:34.28
Code: 0x00000005     Source: Formating Excel Sheet Formating Excel Sheet     Description: BC30179 - enum 'ScriptResults' and enum 'ScriptResults' conflict in class 'ScriptMain'., ScriptMain.vb, 191, 22 End Error
Error: 2013-03-13 17:12:34.29     Code: 0x00000005     Source: Formating Excel Sheet Formating Excel Sheet     Description: The binary code for the script is not found. Please open the script in the
designer by clicking Edit Script button and make sure it builds successfully. End Error Error: 2013-03-13 17:12:51.56     Code: 0x00000004     Source: Checking Alcon Files      Description:
The binary code for the script is not found. Please open the script in the designer by clicking Edit Script button and make sure it builds successfully. End Error Error: 2013-03-13 17:12:51.56     Code: 0xC0024107
Source: Checking Alcon Files      Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:12:27 PM Finished: 5:12:51 PM
Elapsed: 24.336 seconds. The package execution failed. The step failed."
Please give some solution to this.
Thanks in advance

Are you editing this job in SQL 2012? Is it wrapping your paths in \"? Like for example does the command line tab on the step look like this:
/FILE "\"D:\yourPathGoesHere.dtsx\"" /CONFIGFILE "\"D:\yourPathGoesHere.dtsConfig\"" /CHECKPOINTING OFF /REPORTING E
That's the problem I had, and I resolved it by recreating the whole thing via SQL Script and getting rid of all those \" things. I think that is preventing SSIS from looking up the precompiled binaries for your Script Task. So you should edit the command
line manually:
/FILE "D:\yourPathGoesHere.dtsx" /CONFIGFILE "D:\yourPathGoesHere.dtsConfig" /CHECKPOINTING OFF /REPORTING E
Please write back whether that helps you. David Dye's answer didn't help me at all.

Creating new mount points on pre installed Solaris 2.7

Creating new mount points on pre installed Solaris 2.7

Hi,
Thanks for suggestion.
I have checked note 1521371, so as per note I have to provide the locations as given below..
For PI1 (i.e. PI Development)...............
Oracle Base Location : /oracle/PI1
Oracle Home Location : /oracle/PI1/112_64
Inventory Directory : /oracle/PI1
For PI2 (i.e. PI Production)...............
Oracle Base Location : /oracle/PI2
Oracle Home Location : /oracle/PI2/112_64
Inventory Directory : /oracle/PI2
Correct me if I am wrong..
Could you please tell me, does we need to set the ORACLE environmental variables i.e. ORACLE_BASE, ORACLE_HOME and ORACLE_STAGE before start the ORACLE database installation?
Kindly suggest,
Thanks and regards,
Amit....

How can I compile all functions, procedures and packages with a script?

I need to compile all functions, procedures and packages of 5 schemas (users) with a script.
How can I do it?
Thanks!

you can create a script to select all invalid objects in those schemas Since Oracle 8 introduced NDS this approach has struck me as a trifle old fashioned. It's much simpler to loop round the query in PL/SQL and use EXECUTE IMMEDIATE to fire off the DDL statements. No scripts, no muss, no fuss.
Having said that, the problem with this approach and also with using DBMS_UTILITY.COMPILE_SCHEMA is that they do not compile all the invalid objects in dependency order. This may result in programs being invalidated by the subsequent compilation of dependencies. This is due to the introduction of Java into the database.
The UTLRP script is much better, because it (usually) avoids cyclic references. But you still may need to run it more than once.
In general it is better to avoid sledgehammer recompilations (like DBMS_UTILITY.COMPILE_SCHEMA, which starts by invalidating all the objects). If we have twenty invalid objects, nineteen of which are dependencies of the twentieth, we actually only need to recompile the master object, as recompiling it will trigger the recompilation of all the others.
Cheers, APC

Pre-compiled Solaris 10 X*^ mod_jk package

Similar Messages

Maybe you are looking for