Source code files location for wrap - oracle

I want to encrypt a package code.
For do that, I want to use the wrap command.
So for example I have that package:
wrap_try
and when I'm executing that command:
C:\Users\dp>wrap iname=wrap_try.sql
I'm getting that output:
PL/SQL Wrapper: Release 11.2.0.4.0- 64bit Production on Thu May 11 12:59:50 2017
Copyright (c) 1993, 2009, Oracle. All rights reserved.
PL/SQL Wrapper error: Couldn't open input file wrap_try.sql
So I guess it's can't found my file because i need to give it a full path.
But what is the location of all the package\function definition?
My server is windows.
Thanks a lot.

First extract your procedure source to a file, which in your case is 'wrap_try.sql'. Then run your command on the file.dir,
D:\prog>dir
Volume in drive D is Data
Volume Serial Number is 421D-3389
Directory of D:\prog
05/11/2017 08:04 AM <DIR> .
05/11/2017 08:04 AM <DIR> ..
05/11/2017 08:02 AM 30,609 customer_extract_proc.sql
1 File(s) 30,609 bytes
2 Dir(s) 237,137,584,128 bytes free
D:\prog>wrap iname=customer_extract_proc.sql
PL/SQL Wrapper: Release 11.2.0.4.0- 64bit Production on Thu May 11 08:05:02 2017
Copyright (c) 1993, 2009, Oracle. All rights reserved.
Processing customer_extract_proc.sql to customer_extract_proc.plb
D:\prog>dir
Volume in drive D is Data
Volume Serial Number is 421D-3389
Directory of D:\prog
05/11/2017 08:05 AM <DIR> .
05/11/2017 08:05 AM <DIR> ..
05/11/2017 08:05 AM 5,661 customer_extract_proc.plb
05/11/2017 08:02 AM 30,609 customer_extract_proc.sql
2 File(s) 36,270 bytes
2 Dir(s) 237,137,575,936 bytes free

Related

What's the difference between Symbolic Link <=> Junction <=> Shortcut?

In Windows using NTFS file system there are 3 different possiblities to create links to folders.
(For files there are 2 possibilities: hard links and shortcuts.)
A shortcut is a .lnk file which has several hundred bytes that contains the link Information.
But what about the other two possibilities: Symbolic Links <=> Junctions?
According to FreeCommander both link "files" need 30 Byte each.
I'm able to create a junction by using
mklink /j LinkFolderToCreate ExistingFolder
To create a symbolic link I use
mklink /d LinkFolderToCreate ExistingFolder
The dir command gives me the following Output:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Temp\LinkTest\Folder>mklink /d SymLink ..\Link
symbolic link created for SymLink <<===>> ..\Link
C:\Temp\LinkTest\Folder>mklink /j Junction ..\Link
Junction created for Junction <<===>> ..\Link
C:\Temp\LinkTest\Folder>dir
Volume in drive C has no label.
Volume Serial Number is 40A4-35D4
Directory of C:\Temp\LinkTest\Folder
30.08.2018 12:09 <DIR> .
30.08.2018 12:09 <DIR> ..
30.08.2018 12:09 <JUNCTION> Junction [C:\Temp\LinkTest\Link]
30.08.2018 12:09 918 Shortcut.lnk
30.08.2018 12:08 <SYMLINKD> SymLink [..\Link]
1 File(s) 918 bytes
4 Dir(s) 63.696.363.520 bytes free
C:\Temp\LinkTest\Folder>
What are the differences between Symbolic Links and Junctions?
Which one would you take in which case?

creating mercurial repo in directory whose name has dollar signs

I am trying to create a mercurial repository in a directory whose name includes dollar signs. This is an equivalent and simplified example of what i get on windows 10 cmd.exe with mercurial 4.1.3 :
C:\test\dir1>hg init
C:\test\dir1>hg status
C:\test\dir1>cd ../dir$$1
C:\test\dir$$1>hg init
C:\test\dir$$1>hg status
abort: repository C:\test\dir$$1 not found!
so i hope this is clear, the only difference seems to be the dollar signs in the second directory name. thanks in advance!
Mercurial seems to treat dollar signs as an environment variable escape:
C:\test>set X=abc
C:\test>echo $X # Not the shell expanding it, that would be %X%.
$X
C:\test>hg init $X
C:\test>dir
Volume in drive C has no label.
Volume Serial Number is CE8B-D448
Directory of C:\test
11/10/2017 09:27 PM <DIR> .
11/10/2017 09:27 PM <DIR> ..
11/10/2017 09:27 PM <DIR> abc
0 File(s) 0 bytes
3 Dir(s) 53,899,231,232 bytes free
Mercurial has expanded $X as an environment variable. Also:
C:\test>hg init dir$$x
C:\test>dir
Volume in drive C has no label.
Volume Serial Number is CE8B-D448
Directory of C:\test
11/10/2017 09:30 PM <DIR> .
11/10/2017 09:30 PM <DIR> ..
11/10/2017 09:30 PM <DIR> dir$x
0 File(s) 0 bytes
3 Dir(s) 53,899,091,968 bytes free
Two dollar signs insert one dollar sign. When you are in a directory named dir$$x, Mercurial is using dir$x for the name. I found a workaround with hg -R. status, but better to avoid dollar signs.
this has been entered as a Mercurial bug : https://bz.mercurial-scm.org/show_bug.cgi?id=5739

Memory Usage of the c directory files in cmd

So, im running dir c:\ in command prompt and it shows me,
dir c:\
Volume in drive C is OS
Volume Serial Number is BE7A-83CF
Directory of c:\
12/06/2012 04:48 PM Accumedic
02/10/2016 10:27 AM 221,431 avgremover.log
12/23/2015 01:44 AM 3,072 Datacollectors.db
05/08/2012 05:45 PM DELL
02/18/2011 11:46 AM Drivers
02/02/2012 02:17 PM 23,760 FLBS1601.TEST
02/02/2012 02:29 PM 23,760 FLBS1602.TEST
02/18/2011 11:46 AM Install
02/06/2012 11:48 AM 22 Network.bat
07/13/2009 11:20 PM PerfLogs
02/01/2016 03:27 PM Program Files
10/14/2015 03:05 PM Program Files (x86)
12/27/2011 01:34 PM Projects
05/04/2016 08:52 AM SQL_Docs
04/07/2014 04:30 PM temp
07/23/2015 11:19 AM Users
05/04/2016 08:47 AM Windows
5 File(s) 272,045 bytes
12 Dir(s) 1,979,822,080 bytes free
Is there a command to see the disk usage of each of the files, instead of just the total? Preferably, in a similar format, and not individually looking each one up.
It is showing you the sizes of the files in the directory. From your question:
02/10/2016 10:27 AM 221,431 avgremover.log
12/23/2015 01:44 AM 3,072 Datacollectors.db
This is telling you that avgremover.log is 221,431 bytes in size. Most of the lines in your example don't have a number because they are directories. dir doesn't list a size for them.

Where is my CAB file?

I am making a CAB file from a Directive text file for multiple file compression. Eveything seems to be working fine; however, I cannot find my newly created CAB file. This is my first attempt at doing this so I know it has to be something I am doing wrong. The DDF file I have created seems to be working fine, there is just no file I can find after. Here is what I am putting in the command:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\lazocd>makecab.exe /F C:\Users\lazocd\Desktop\DataLibrary\ss64.ddf /L C
:\Users\lazocd\Desktop
Cabinet Maker - Lossless Data Compression Tool
1,134,955 bytes in 7 files
Total files: 7
Bytes before: 1,134,955
Bytes after: 810,621
After/Before: 71.42% compression
Time: 0.44 seconds ( 0 hr 0 min 0.44 sec)
Throughput: 2507.59 Kb/second
Found It! It puts it into its own directory by default called disk1. Just needed to search harder. Thanks for the views anyways!

What happens when a path has no directory separator?

C:WProgram Files
Anyone knows such kind of location? How is it processed in programmes, the same as \ ?
A path with a drive letter and then a relative path is resolved relative to the current directory for that drive letter.
Windows and MS-DOS systems keep track of the current directory for each drive letter separately.
For example:
G:\>dir c:
Volume in drive C is System
Volume Serial Number is A09A-AD9C
Directory of C:\
06/12/2008 02:44 PM 0 AUTOEXEC.BAT
06/12/2008 02:44 PM 0 CONFIG.SYS
08/25/2008 02:22 PM <DIR> Documents and Settings
12/09/2009 12:45 PM <DIR> Program Files
[snip]
G:\>cd "c:\Program Files"
G:\>dir c:
Volume in drive C is System
Volume Serial Number is A09A-AD9C
Directory of C:\Program Files
12/09/2009 12:45 PM <DIR> .
12/09/2009 12:45 PM <DIR> ..
05/14/2010 11:38 AM <DIR> 7-Zip
12/13/2010 01:49 AM <DIR> Adobe
[snip]
G:\>dir c:Adobe
Volume in drive C is System
Volume Serial Number is A09A-AD9C
Directory of C:\Program Files\Adobe
12/13/2010 01:49 AM <DIR> .
12/13/2010 01:49 AM <DIR> ..
01/25/2010 01:45 AM <DIR> Reader 8.0
12/13/2010 01:49 AM <DIR> Reader 9.0
The path c:Adobe became the same as C:\Program Files\Adobe because that was the current directory for the C drive, even though the current drive was actually the G drive.

Resources