Does anybody know how can I create a text file in OpenVMS without the version extension? I need to take some logs from this server and edit them in a Linux server. Until know the downloaded file from OpenVMS server cannot be opened.
Regards,
Theodore
Did you google your problem? You would find answers to help you along.
As indicated you cannot get rid of the file version number on the OpenVMS side.
You can edit those file on the Linux side easily - folks do it all the time.
You indicate the file cannot be opened. What is the error message?
Best is to copy&paste the exact command used and the returned message.
On Linux You probably just need to escape the ";" with a backslash to avoid it from terminating the command fragment. Or you can put the whole name in quotes.
If you don't like that, then you may need to look at the tool used to access (Samba?), package (zip?) or transfer the file (ftp/sftp). They are likely to have a setting to honor or discard the file version.
Since you fail to indicated exactly what you are doign, we cannot help until we know.
The ZIP on my OpenVMS server has options -
zip -h
Info-ZIP - Zip 3.0 (July 5th 2008).
-w store file version numbers -ww store file version numbers as ".nnn"
Good luck!
Hein
Related
When i try to start SQLDeveloper, it is giving me the following error in command prompt:
Error: This product requires a Java(TM) Platform 5.0 runtime.
You are using 1.4.2-b28 from C:\j2sdk1.4.2\jre
But my JAVA_HOME is set to java 6
JAVA_HOME=C:\Program Files\Java\jdk1.6.0_32
Can anyone explain what exactly to do to resolve this?
Oracle SQL Developer uses a configuration file named products.conf which is situated at your roaming directory.
If you are using Windows 7 then the directory path will be:
C:\Users\\AppData\Roaming\sqldeveloper\1.0.0.0.0
Delete whole sqldeveloper directory from C:\Users\\AppData\Roaming\
Re run sqldeveloper executable, this will prompt for jdk home
Select jdk home. i.e C:\Program Files\Java\jdk1.7.0_55
Enjoy!
In my case i had 2 folders under C:\Users\username\AppData\Roaming\
sqldeveloper
SQL developer
after removing both of them and launching installation dir\sqldeveloper\sqldeveloper\bin\sqldeveloper64.exe it worked.
True acknowledgement / attribution belongs to Vishal at the following URL:
http://vishalorcl.blogspot.com/2012/12/sql-developer-from-11201-client-software.html. It describes in detail how to resolve this problem. From the page:
I am running Oracle 11g version of SQLDeveloper. I have same problem
noted above, after fresh install of Oracle. The summary is that
SQLDeveloper seems to require the Java 32-bit JDK.
Install 32-bit jdk V7 from Oracle:
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
There is a sqldeveloper.conf file located in
C:\app\UserName\product\11.2.0\dbhome_1\sqldeveloper\sqldeveloper\bin
In the file change pathname within the line at end of file:
SetJavaHome C:\app\admin\product\11.2.0\client_1\jdk
To point to pathname of the jdk install directory; also sometimes
known as JAVA_HOME.
I had this problem too!
you should go to: C:\Users-your user name-\AppData\Roaming\sqldeveloper-version of your sql developer-
there is a file named product.conf there. Right click on it and edit it with notepad in the document change the address of java home and save it.
Done!
In my case, none of the other suggestions worked. Instead, I moved the installation directory from
c:\sqldeveloper
to
anything else
And things worked again. Perhaps, some Windows registry value got broken in an unfixable way...
I don't think SQLDeveloper uses the environment variable. There should be a .conf file that contains a reference to the JDK directory.
I solved this by deleting the folder /home/USERNAME/.sqldeveloper
After that, I started SQLDeveloper and without typing anything, it found the right java-version and started without complaining :-)
So, if you don't want to delete the whole folder, maybe search there for the file which defines the java-version :-)
edit: just found that:
"Type the full pathname of a J2SE installation (or Ctrl-C to quit), the path
will be stored in ~/.sqldeveloper/jdk"
check the version of java that you are installing to you Pc the error show that you are using 4 so uninstall the java that you have then install a new one that is version higher than 5
Removing the instances from the registry worked for me.
Can anyone tell me from where I can download openldapforwindows.exe (OpenLDAP for windows) version 2.2.29? I tried various pages, but I was not able to get this particular version
I suggest you solve the problem instead of downgrading.
Your schema files need to be in DOS format not Unix format, i.e. line-terminated by \r\n.
you can download openldap for windows from http://www.userbooster.de/en/download/openldap-for-windows.aspx
I have a thesis project that requires a project log to be submitted along with my final paper. As part of that log I'd like to include the Bazaar revision log and all the messages that it contains but I'll need to have them in a printable format.
I was unable to find any export feature in the Bazaar Explorer tool but I hope it's still possible to do somehow. Any thoughts?
Thanks!
You can get log in the text format using command-line: bzr log > log.txt or via Bazaar Explorer with running All Commands dialog and select log command there and then copy the log from status window. Read the help for log command to find the appropriate options. You may want to use -n0 option and maybe --forward one.
For completeness, you can use the bzr-xmloutput plugin to get an xml version and then process that into exactly what you want.
I am working with LaTeX on Vista using TeXnicCenter 2.0 Alpha 3 (build 1118) having installed MiKTeX 2.8. I want to use code highlighting for Objective-C and read here that the minted package is great.
I installed Python 2.7 and pygmentize as told in the minted documentation. I also set the compiler option -shell-escape in TeXnicCenter. The compiler finds the pygmentize script but the following error occurs.
File "C:\Python27\Scripts\pygmentize.exe", line 1 SyntaxError: Non-ASCII character '\x90' in file C:\Python27\Scripts\pygmentize.exe on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details! LaTeX Error: File `Test.out.pyg' not found. Type X to quit or to proceed, or enter new name. (Default extension: out.pyg) Enter file name: ! Emergency stop.
I cannot figure out how to fix the problem. I tried saving the tex file as ANSI or UTF-8.
The only additions I made to the tex file are the package include
\usepackage{minted}
and this simple example from the minted documentation.
\mint{python}|import this|
The minted documentation is outdated: newer versions of Pygments apparently include a Windows executable pygmentize.exe (unfortunately, their Trac is currently offline so I can’t look up the relevant revision which changed that).
This means that the fix mentioned in the documentation should be redundant. Therefore, try the following steps:
Remove the pygmentize.cmd script entirely (best not delete it yet – just rename it). Try if minted now works.
If that doesn’s work, put the following into the pygmentize.cmd:
#echo off
set PYTHONPATH=C:\Python27
%PYTHONPATH%\Scripts\pygmentize.exe %*
i.e. don’t invoke the *.exe file via the Python interpreter.
Unfortunately, I can’t test this now since I don’t have Windows here. But one of the options should work.
I have access to a remote Solaris terminal which crashes occasionally, and I have to ask someone with physical access to boot the machine up, which it does successfully. I would like to know which tools/files should I look at to find out the cause of the crash so that I can make the necessary configuration changes and avoid it in the future.
What tools you can use will depend on what version of solaris you have running and what the actual problem
is. The first thing to do is check the system console (which it sounds like you don't have access to) and the /var/adm/messages file. This file is updated with system messages and the newest will appear at the end.
Next, you can look for a system core file. If a core file is created, it would be in /var/crash/hostname where "hostname" is the name of the machine.
If you have an actual core file in the /var/crash/hostname directory, this set of commands will give you a good
string to search google with:
# cd /var/crash/hostname
Replace "hostname" with the hostname of your machine.
# mdb -k unix.0 vmcore.0
If you have multiple core files, select the most recent version.
> ::status
This should give you a panic message, cut and paste that into google and see what you can find.
For more core file analysis read this:
http://cuddletech.com/blog/pivot/entry.php?id=965