cancel
Showing results for 
Search instead for 
Did you mean: 

Starting the database server with -c %%

1,804

1) If I run dbsrv12.exe -c 30%% then

a) For 12.0.1.3537 - OK

    2: -c
3: 30%%
...
SQL Anywhere Network Server Version 12.0.1.3537
...
Running Windows 7 Build 7601 Service Pack 1 on X86_64
Server built for X86_64 processor architecture
2511152K of memory used for caching
Minimum cache size: 2511152K, maximum cache size: 7529760K
b) For 12.0.1.4178: Invalid database server command line error

2) If I run dbsrv12.exe -c 30% then
a) For 12.0.1.3537 - OK
b) For 12.0.1.4178 - OK

    2: -c
3: 30%
...
SQL Anywhere Network Server Version 12.0.1.4178
...
Running Windows 7 Build 7601 Service Pack 1 on X86_64
Server built for X86_64 processor architecture
2511152K of memory used for caching
Minimum cache size: 2511152K, maximum cache size: 7529760K
Is it bug? For 12.0.1.3537 or for 12.0.1.4178 ?

Accepted Solutions (1)

Accepted Solutions (1)

johnsmirnios
Participant

You want one "%" sign to make it to the server. If the server is invoked from a shell (cmd.exe on Windows), "%%" gets converted to "%" by the shell because "%" is used for environment variable substitutions. You appear to be invoking the server without using a shell so you only want -c 30%.

To avoid issues with shells and %, you could just use -c 30p.

-john.

Former Member

Fortunately, "p" in this case doesn't stand for "petabytes." That would be a big cache.

Answers (0)